Skip to main content
The Abigail API uses a credit-based billing system. You purchase credits, and usage is deducted in real-time based on token consumption. LLM usage is never blocked — only document exports are credit-gated.

How billing works

  1. Purchase a credit package (or receive $25 welcome credits on signup)
  2. Every API call that uses AI consumes tokens (input + output)
  3. Token costs are deducted from your credit balance automatically
  4. Every response includes balance headers so you can track spending

Token pricing

A typical /analyze call processes ~2,000 input tokens and ~1,500 output tokens, costing approximately $0.40 per analysis.

Model multiplier

Your account has a model version setting (default 1.0x) that multiplies base token prices. Higher-capability models may have higher multipliers.

Credit packages

Custom amounts are also supported (1:1 credits, no bonus). New accounts receive $25 in welcome credits to get started.

Document export pricing

Document exports (DOCX downloads) are credit-gated — the API returns HTTP 402 if your balance is insufficient.
Document exports are the only operations that block on insufficient credits. All LLM-based operations (analyze, examiner lookup) always complete regardless of balance.

What is free?

These operations are never billed:
  • GET /v1/openclaw/lookup/{app_number} — application metadata
  • GET /v1/openclaw/deadlines/{app_number} — response deadlines
  • GET /v1/openclaw/draft-roa/status/{job_id} — polling draft status
  • GET /v1/openclaw/download/{job_id} — downloading a completed DOCX (the draft submission is billed, not the download)

Usage tracking headers

Every response from authenticated endpoints includes these headers:

Balance status thresholds

When balance is low or below, responses also include:

Handling 402 responses

When a document export is blocked for insufficient credits:
Your agent should inform the user to purchase credits and retry.

Rate limits

Rate limits are per API key (authenticated) or per IP (free endpoints).

Rate limit headers

Handling 429 responses