Credit debit
Records credits debited, remaining balance, settlement reference, payment request reference, and the ledger entry tied to the agent task.
TokenOps · receipts and callbacks
Receipts and callbacks for agent-paid work.
A paid agent run should not disappear into a black box. TokenOps returns an operating trail: credit debit, evidence status, result package URL, usage receipt, callback payload, and next available action.
Receipt ledger
Every TokenOps run leaves a clean usage record.
The receipt ledger records credits funded, credits debited, work performed, result state, callback readiness, and settlement references for agent-paid work.
Evidence state
Preserves whether the run was sufficient, partial, or insufficient, with score, received inputs, uploaded file manifest, and open items.
Result link
Connects the usage receipt to the TokenOps result package or preliminary data request so the agent has a durable return path.
Callback payload
The return path should be machine-readable.
When a paid task is ready, partial, failed, or delivered, the callback payload tells the requesting agent where to retrieve the result, which receipt was issued, what the delivery state is, and which actions are available next.
{
"payload_type": "agent_callback_payload",
"event_type": "task_result_ready",
"requested_tool": "tokenops",
"result_status": "ready",
"result_url": "https://os.weverlabs.com/api/agents/tasks/demo-token/result",
"receipt_url": "https://os.weverlabs.com/api/agents/receipts/usage_demo_20260602_001",
"delivery": {
"callback_status": "ready",
"attempt_count": 0
}
}Continuation contract
The next agent should not have to guess.
A useful result does not just say done. It says what was done, what evidence supports it, what remains open, where the receipt lives, whether callback delivery succeeded, and what the next system can do.
Ready
Result package is available, receipt is issued, callback payload can be delivered, and downstream work can continue.
Partial
The OS returns a preliminary package and data request instead of pretending the evidence is complete. Honest rails beat shiny nonsense.
Retry
If callback delivery fails, the payload can expose retry state, last attempt, and next retry guidance without leaking secrets.
Task ledger
Usage now points back to the run ledger.
Receipts and settlement references are stronger when they tie back to a paid agent task run, state events, and result attestation. The OS can show what was quoted, funded, run, debited, packaged, receipted, and delivered.
Callback recovery
A callback failure can become a recoverable exception.
If a result package is ready but callback delivery fails, the receipt rail can point to an exception ticket and replay package instead of hiding the failure behind a generic pending state.
{
"callback_status": "failed",
"exception_type": "callback_failure",
"recovery_action": "retry_callback",
"replay_package_url": "https://os.weverlabs.com/api/agents/tasks/.../replay-package"
}Settlement and usage receipts
One receipt funds credits. The other records work.
Settlement receipts record provider-confirmed credit funding. Usage receipts record credits consumed by TokenOps work. Result Contract v2 links both so the next agent can follow the trail without guessing.
agent_settlement_receipt
→ credit_entitlement
→ tokenops_usage_receipt
→ agent_result_contractAgent-to-agent economy
Make the return path as real as the intake path.
TokenOps now has public contracts for result packages, usage receipts, evidence file manifests, and callback payloads.
Status rail
Receipts should not be the only thing agents can retrieve.
The status response lets an agent ask where the work is: quoted, funded, queued, partial, ready, delivered, or failed. It points back to the credit entitlement, result package, receipt, and callback state.
quote_id
credit_entitlement_id
work_order_id
result_status
receipt_url
callback_status
next_actions