Token Pricing#

Every authenticated API request consumes tokens. Token usage is tracked per identity and aggregated monthly. Only successful responses (2xx status codes) consume tokens — failed requests (4xx/5xx) are free.

Each response includes an X-Tokens-Consumed header indicating how many tokens were charged for that request.

HTTP/1.1 200 OK
X-Tokens-Consumed: 10
Content-Type: application/json

Token costs per endpoint are also displayed in the [API Reference](/docs/api/reference/) as badges next to each operation.

API Request Token Costs#

Case Management#

Endpoint	Method	Tokens
`/v1/cases`	POST	10
`/v1/cases`	GET	10
`/v1/cases/{id}`	GET	10
`/v1/cases/{id}`	PUT	10
`/v1/cases/{id}`	DELETE	5

SOAP Notes#

Endpoint	Method	Tokens
`/v1/cases/{id}/soap-notes`	GET	10
`/v1/cases/{id}/soap-notes`	POST	10
`/v1/cases/{id}/soap-notes/{noteId}`	GET	10
`/v1/cases/{id}/soap-notes/{noteId}`	PUT	10
`/v1/cases/{id}/soap-notes/{noteId}`	DELETE	5

Attachments#

Endpoint	Method	Tokens
`/v1/cases/attachments`	POST	10
`/v1/cases/attachments`	GET	5
`/v1/cases/attachments/{attachmentId}`	GET	5
`/v1/cases/attachments/{attachmentId}`	PUT	5
`/v1/cases/attachments/{attachmentId}`	DELETE	5

Reference Data#

Endpoint	Method	Tokens
`/v1/animal-types`	GET	5
`/v1/breeds`	GET	5
`/v1/breeds/{breedId}`	GET	5
`/v1/diseases`	GET	5
`/v1/diseases/{diseaseId}`	GET	5
`/v1/diseases/{diseaseId}/treatment-protocols`	GET	10
`/v1/diseases/{diseaseId}/treatment-protocols/{id}/treatments`	GET	10
`/v1/drug-substances`	GET	5
`/v1/drug-substances/{drugSubstanceId}`	GET	5
`/v1/drug-substances/{drugSubstanceId}/doses`	GET	5
`/v1/symptoms`	GET	5
`/v1/symptom-type-categories`	GET	5
`/v1/geographical-areas`	GET	5
`/v1/sources`	GET	5
`/v1/sources/{sourceId}`	GET	5

Background Processing Tokens#

In addition to per-request tokens, certain operations trigger background AI processing that consumes additional tokens. These are charged automatically and accumulated on the resource.

Operation	Tokens	Notes
AI Extraction	1,000	Triggered automatically when a case is created or notes are updated. Includes sanitization and diagnosis calculation.
Attachment Processing	1,000	Per attachment. Triggered when an attachment is uploaded.
SOAP Note Generation	500	Per generation. Triggered by `POST /cases/{id}/soap-notes`.

Resource-Level Token Tracking#

Background processing tokens are tracked directly on the resource, making it easy for integrators to monitor per-case and per-attachment AI costs. Case and attachment response objects include a tokens_consumed field showing the total tokens consumed by background processing for that resource:

Case: Accumulates tokens from AI extraction (1,000 per extraction), re-extractions on edit, and SOAP note generation (500 each).
Attachment: Shows tokens consumed by attachment processing (1,000 per attachment).

{
  "id": "case-123",
  "status": "COMPLETED",
  "tokens_consumed": 1500,
  ...
}

Typical Session Estimate#

The following example shows a typical case session with one edit and a SOAP note generation:

POST /v1/cases (create) — 10 tokens
AI Extraction (automatic) — 1,000 tokens
User edits freetext — PUT /v1/cases/{id} — 10 tokens
AI Re-extraction (automatic) — 1,000 tokens
SOAP note generation — POST /v1/cases/{id}/soap-notes — 10 tokens (API) + 500 tokens (generation)
Reference data lookups (~30 requests) — ~175 tokens

Category	Tokens
Case CRUD	~30
AI Processing (x2)	~2,000
SOAP Note Generation	~500
Reference Data (~30 requests)	~175
Total	~2,705

Purchasing Tokens#

Tokens can be purchased in packages. Contact us to discuss your needs and arrange a token package.