Skip to main content
Plangrep uses a credit-based billing model. Credits are charged per page processed, with different rates for drawing pages (construction plan sheets) versus document pages (specifications, addenda, or other documents).

​
Credit Rates

Page typeDefault credits per page
Drawing page10 credits
Document page1 credit
Your organization’s actual rates are shown in the drawingCreditsPerPage and documentCreditsPerPage fields of the OpenApiProfile object returned by the workspace keys endpoint. Use those values — not the defaults above — when estimating costs for your specific account.

​
OpenApiProfile fields

FieldDescription
drawingCreditsPerPageCredits charged per drawing page for your organization
documentCreditsPerPageCredits charged per document page for your organization
enabledWhether API access is currently enabled for your organization
jobPageLimitMaximum pages allowed per job for your organization
retentionDaysNumber of days job results are retained before deletion
updatedAtISO 8601 timestamp of the most recent profile update

​
When Credits Are Charged

Credits move through two stages during a job’s lifecycle:
1

Reserved at preflight

When a job transitions to preflighting, Plangrep estimates the total pages based on declared file sizes and reserves (creditsReserved) that amount from your balance. This prevents other jobs from over-drawing your account concurrently.
2

Debited on success

As each page is successfully processed, credits are debited (creditsDebited) from your balance. Only successfully processed pages consume credits — failed pages are not charged.
3

Reservation released

When the job completes, any difference between the reserved amount and the actual debited amount is released back to your available balance.

​
Project Creation Billing

Creating a project charges a small credit amount to provision the underlying runtime. The ProjectCreateResponse includes a billing object with:
FieldDescription
creditsChargedCredits consumed to create this project
availableCreditsYour organization’s credit balance before the charge was applied

​
Blocked Jobs

If your organization’s credit balance is exhausted while a job is processing, the job transitions to blocked_insufficient_credits and pauses.
1

Add credits

Purchase additional credits through your account dashboard or contact your account manager.
2

Resume the job

Call the resume endpoint to continue processing from where it left off:
POST /api/open/v1/jobs/{jobId}/resume
Authorization: Bearer {your_api_key}
Jobs that remain in blocked_insufficient_credits until their TTL elapses will transition to expired. Add credits and resume promptly to avoid losing progress.

​
Credit Fields in API Responses

​
On every Job object (Billing)

FieldDescription
creditsDebitedCredits charged for successfully processed pages so far
creditsReservedCredits currently held in reserve for this job
drawingCreditsPerPageRate applied to drawing pages for this job
documentCreditsPerPageRate applied to document pages for this job
drawingPageCountDrawing pages processed so far
documentPageCountDocument pages processed so far
successfulPageCountTotal pages that completed without error

​
On every Result object (ResultUsage)

The usage field in the result JSON contains the same breakdown, frozen at the time the result was generated. This is the immutable record of what was charged for this job. See Results for the full ResultUsage schema.
Contact your account manager or the Plangrep support team for questions about credit packages, bulk pricing, and organization-level limits.