Inference receipts

An inference receipt is a deterministic, auditable accounting record for a job — what model ran, how many tokens it billed, what was charged, and what reward accrued. It is billing evidence, not a claim about the world.

What a receipt is

Every completed or failed inference job produces a receipt — whether it came from the signed-in web console or the programmatic API. It records the deterministic economic outcome of that job in $BASIS base units so the charge, the protocol fee, and the worker reward can be recomputed and checked. Worker rewards settle on Base only once the $BASIS token and the reward distributor contract are live — until then accrual is honest but unsettled.

Accounting, not verification

A receipt is an accounting record. It is not a verdict, a rating, or a verification of any claim. It states what was billed and what was paid for a single job — nothing more.

No prompt or output text — ever

A receipt records the model, token counts, worker, pricing snapshot, and settlement accounting. It never contains your prompt or the model's output text — only the deterministic economic facts of the job are hashed and stored.

Metered vs. paid

Every completed or failed job records a receipt. A gateway-served (proxied) job has no contributor worker wallet, so it is metered, not paid: workerWallet is empty and workerRewardRaw is "0". Only an orchestrator-routed job served by a contributor GPU with a valid EVM reward address can earn $BASIS.

Receipt fields

The economic core below is immutable and is what the receiptHash is computed over. All raw amounts are $BASIS base units carried as decimal strings.

Economic core (hashed)

Field	Type	Notes
receiptVersion	number	Schema version of the receipt.
jobId	string	Unique business key for the job. Duplicates are rejected.
userId	string \| null	Identifier for the caller, if known.
userWallet	string \| null	Caller's wallet, if supplied.
workerId	string	The worker that served the job.
workerWallet	string	Worker's EVM reward address (empty for gateway-served jobs).
modelId	string	Model served, e.g. basis-default.
promptTokens	number	Prompt tokens billed.
outputTokens	number	Output tokens billed.
latencyMs	number	Observed latency in milliseconds.
qualityBps	number	Quality factor in bps.
uptimeBps	number	Worker uptime factor in bps.
latencyBps	number	Latency factor in bps.
modelMultiplierBps	number	Pricing multiplier in bps (10000 = 1x).
totalChargedRaw	string	Total charged, in $BASIS base units. INVARIANT: equals pricing.basisRequiredRaw.
workerRewardRaw	string	Worker reward, in $BASIS base units. "0" for any non-completed status and for gateway-served jobs.
protocolFeeRaw	string	Protocol fee (per-job burn share), in $BASIS base units.
pricing	PricingSnapshot	The locked pricing snapshot: pricingEpochId, pricingSnapshotHash, usageCreditsRaw, basisPerCreditRaw, basisRequiredRaw, priceSource, and the utilization/supply/demand/provider-floor multipliers. Hashed — the receipt commits to the exact price the job was reserved at.
tokenSymbol	string	BASIS.
tokenAddress	string	Empty while the token is pending deployment.
chainId	number	Base chain id (8453).
createdAt	string	ISO 8601 timestamp the job was recorded.

Envelope (excluded from the hash)

Field	Type	Notes
receiptHash	string	SHA-256 over the canonical economic core. Unique; duplicates rejected.
receiptSignature	string \| null	Optional signature over the receipt envelope.
status	ReceiptStatus	Lifecycle status (see below). Excluded from the hash.
settlementBatchId	string \| null	Batch that settled the reward, once batched. Excluded from the hash.
settlementTxHash	string \| null	Base tx hash, once settled. Excluded from the hash.
quoteId	string \| null	Pricing-quote linkage. Excluded from the hash.
paymentQuoteId	string \| null	Payment-quote linkage. Excluded from the hash.
payment	PaymentSnapshot \| null	Payment-route pointers (provider, swap/deposit tx hashes, status), if any. Excluded from the hash.

Statuses

A receipt carries one of six statuses. Status lives in the envelope, so it can move through the lifecycle without changing the receipt hash.

completedThe job finished and produced output. The economic core is final and the reward (if any) is accrued.

failedThe job did not complete. The reward is zero and the user is not overcharged.

rejected_qualityOutput was rejected on quality grounds. The reward is zero.

rejected_workerThe job was rejected at the worker level. The reward is zero.

pending_settlementA completed job whose accrued reward is queued to be settled on Base.

settledThe reward has been settled on Base. settlementBatchId and settlementTxHash point at the on-chain record.

receiptHash determinism

The receiptHash is the SHA-256 of the canonical JSON of the immutable economic core. Canonical JSON means recursively sorted keys and no incidental whitespace, so the same economic outcome always hashes to the same value and anyone can recompute it.

Sample receipt hash

receiptHash0x9f2c4d7a1b8e…0e7b4c1f

The hash excludes the envelope — status, receiptSignature, and the settlement pointers — so it stays stable as the receipt moves from completed to settled. A duplicate jobId or receiptHash is rejected, so a job is never recorded or paid twice.

Looking up a receipt

Fetch a single receipt by its hash. The response includes the receipt and a verified flag — the server recomputes the hash and reports whether it matches.

bash

curl -s https://basis.watch/api/inference/receipts/<receipt_hash>

# { "receipt": { ... }, "verified": true }

List recent receipts:

bash

curl -s https://basis.watch/api/inference/receipts