Usage and cost

Read usage, not the docs, for your real cost

Every response carries a usage object with the exact input and output spatial-token counts you were billed for, plus projected cost. That is authoritative for a request in a way no published estimate can be, because token counts depend on your files.

What is billed

Only successful 2xx results reach the meter. Failed requests are recorded against their request_id so you can debug them, and are never billed. Uploaded file bytes count as input tokens; returned JSON counts as output.

The request ceiling is not an allowance

Accounts default to 100,000 requests per billing period. It is an abuse and safety control, not included usage, and it can be raised for an account. Hitting it is not the same as running out of credit — there is no credit.

How the pricing calculator was measured

The file calculator on the pricing page is not a guess. A sample of public, permissively licensed STEP, IGES, DXF, PDF, and SVG files was run through the Four Cad converter with the API's own accounting, and a subset was sent through the live metered endpoint to confirm the ledger matched byte for byte. Input tokens are exact (bytes / 4). Output tokens are reported at the sample median and p90 for the default structured contract; the sample date and size are shown next to the calculator, and the manifest (source URL and licence per file), raw records, and write-up are published in the repository under docs/.

• STEP and IGES output is a small, stable fraction of input — cost tracks file size closely
• PDF, DXF, and SVG output varies several-fold with drawing content — treat the p90 as the planning number
• The both contract appends a point cloud whose size does not track file size, so it is not estimated