v2.4 CURRENT PROTOCOLPay as You Go

Credit Model

On Incapon one credit equals one US dollar, and every tool spends from the team's single balance. Pricing follows the "pay only the cost" principle: for jobs that call a model, such as Altyazı, we deduct the provider's list price and add no markup. Jobs that run on our own infrastructure, such as Detector and PDF operations, are charged at a fixed unit price.

How a job is charged

  1. Estimate and reserve. When a job starts, its estimated cost is reserved from the balance. OCR on a 40-page PDF reserves 40 × $0.01 = $0.40. If the balance does not cover the estimate, the request is rejected with 402 INSUFFICIENT_CREDITS and nothing runs.
  2. Actual cost. When the job finishes, actual consumption is calculated. For Altyazı this is the minutes processed times the model's per-minute price.
  3. Settlement. The difference between the reserved and the actual amount returns to the balance immediately. Failed jobs are not charged.

Example costs

JobCalculationTotal
Hourly Detector monitor, 30 days720 × $0.002$1.44
Same monitor, visual diff on720 × $0.01$7.20
100 pages OCR + redaction100 × ($0.01 + $0.005)$1.50
Signature comparison1 × $0.40$0.40
60-minute video, Altyazı60 × ~$0.006~$0.36

So the $15 welcome credit covers ten hourly monitors for a month, or roughly a thousand pages of OCR and redaction.

Read the balance

GET /credits/balance costs no credits and only needs the credits:read scope.

curl https://api.incapon.com/v2.4/credits/balance \
  -H "Authorization: Bearer $INCAPON_API_KEY"

available_usd is the amount usable for new jobs; reserved_usd is the part held for jobs that have not finished yet.

Keep costs under control

1. Match check frequency to the job

Checking a page that changes once a day every five minutes multiplies its cost by 288. Set the frequency to how fast the value really changes.

2. Turn on visual diff only when needed

Visual diff is five times as expensive. For most price and stock tracking, DOM comparison with a CSS selector is enough.

3. Experiment with a test key

inc_test_... keys spend no credits. Run the whole flow with one before taking the integration live.

4. Track usage per job

The usage breakdown under Settings → Billing lists every job with its tool, key and unit cost, and can be exported as CSV.

Next Steps & Guides

Was this guide helpful?

Your feedback helps us improve our documentation.