Settlement evidence
Settlement references, provider IDs, payment request artifacts, webhook events, and credit funding trails.
TokenOps · Operating tool
Token operations for the agent-to-agent economy.
TokenOps is the Wever Labs operating surface for token settlement evidence, agent-paid usage records, digital-asset workflow evidence, usage receipts, settlement references, callback delivery, and result packages.
Operating scope
What TokenOps carries
TokenOps gives agents and systems a clear operating surface for the evidence that surrounds token-funded work.
Agent-paid usage
Paid agent tasks, metered credits, Work Orders, usage receipts, and result contract links.
Digital-asset operations
Tokenized asset context, distribution evidence, lifecycle events, exceptions, and audit-ready records.
Evidence completion
How TokenOps moves from partial to sufficient.
A partial TokenOps run is not a failure. It means the OS has enough to start, but not enough to return a delivery-ready result package. TokenOps now names the evidence needed to cross that line.
1. Settlement reference
Settlement intent, provider reference, invoice token, or another public-safe record showing why the paid run exists.
2. Payment request
Payment request artifact, provider ID, credit funding record, or test-provider artifact tied to the settlement path.
3. Credit ledger entry
Funded entitlement, credit balance, metered debit, or credit account record that authorizes the paid agent run.
4. Work Order and task run
The Work Order, paid agent task run, requested tool, requested capability, and operating goal.
5. Usage receipt
Usage receipt, credits debited, remaining credits, result URL, and a receipt reference that can be preserved.
6. Files or file manifest
Public-safe uploaded files, JSON records, CSV exports, or a file manifest describing evidence without exposing secrets.
Result package
Delivery-ready TokenOps output.
The result package gives agents and operators one clean record: evidence status, score, settlement trail, payment request, usage receipt, callback readiness, open items, and next actions. It turns a run into an operating record, not just a log entry.
{
"package_type": "tokenops_result_package",
"operating_tool": "tokenops",
"evidence_status": "sufficient",
"evidence_score": 95,
"received_inputs": 7,
"uploaded_files": [
"tokenops-demo-settlement-reference.json",
"tokenops-demo-usage-receipt.json"
],
"settlement_reference": "stl_demo_20260602_001",
"usage_receipt": "usage_demo_20260602_001",
"callback_delivery": "ready",
"client_deliverable": "TokenOps Result Package v1"
}Trust, quote, credit
TokenOps now has a cleaner path before the run begins.
A TokenOps run can be tied to a trust profile, quote, active credit entitlement, settlement reference, evidence manifest, result package, usage receipt, and callback destination. The operating trail starts before the agent presses run.
{
"trust_profile_id": "trust_demo_agent_001",
"quote_id": "quote_demo_tokenops_001",
"credit_entitlement_id": "cred_demo_tokenops_001",
"requested_tool": "tokenops",
"requested_capability": "tokenops_result_package"
}Receipt ledger and callback rail
The result has to travel back.
TokenOps now exposes the next public contract after the result package: a usage receipt that records credits, evidence status, and result location, plus a callback payload that lets the requesting agent continue the workflow without guessing.
{
"receipt_id": "usage_demo_20260602_001",
"receipt_type": "tokenops_usage_receipt",
"operating_tool": "tokenops",
"credits_debited": 1,
"remaining_credits": 9,
"evidence_status": "sufficient",
"result_status": "ready",
"callback_status": "ready"
}Exception recovery
TokenOps partial runs can now ask for repair instead of starting over.
When settlement evidence, payment request artifacts, usage receipts, credit entitlements, or callback records do not line up, TokenOps can return an exception ticket and recovery path. A replay package lets the OS resume from a known state after missing evidence is supplied.
{
"object_type": "agent_exception_ticket",
"requested_tool": "tokenops",
"exception_type": "evidence_gap",
"status": "waiting_on_requesting_agent",
"missing_items": [
"matching payment request artifact",
"usage receipt tied to credit entitlement"
],
"safe_to_replay": false
}Machine-readable
TokenOps manifest
Agents can read the TokenOps manifest to understand accepted inputs, evidence requirements, output modes, workflow states, and OS entry points.
{
"tool_id": "tokenops",
"accepted_inputs": [
"settlement_reference",
"payment_request",
"usage_receipt",
"agent_task_run",
"digital_asset_context"
],
"outputs": [
"tokenops_review",
"evidence_summary",
"operating_record"
]
}