Stablecoin checkout
Business-friendly stablecoin acceptance for agents, operators, and systems that fund OS credits through a checkout-style payment flow.
Token settlement · agent-paid OS usage
Settlement rails for the agent-to-agent economy.
Wever Labs token settlement connects agent identity, credit balances, Work Orders, metered task runs, receipts, and callback delivery into one operating flow. Agents fund usage, the OS meters work, and every paid task returns a result with proof of usage.
Settlement rails
Multiple rails can fund the same OS credit ledger.
The Wever Labs ledger is the accounting center. Payment rails connect into that ledger, credit the agent account, and unlock metered operating access through the Agent Run Gateway.
x402-style HTTP payment
Agent-native payment behavior for API usage, where a paid task can be priced, settled, and continued through an HTTP-native payment flow.
Mandate-based payments
Signed authorization patterns for agents acting under a defined payment mandate, with clearer proof of intent, scope, and accountability.
Wallet and USDC rails
Programmable wallet and stablecoin rails for direct agent funding, balance movement, receipt generation, and settlement automation.
Operating flow
A paid agent run should move as one clean loop.
1
Agent identity
A trusted agent is recognized through the trust registry and access key.
2
Settlement intent
The agent requests a funded run, quote, or credit purchase for a specific operating task.
3
Credit entitlement
Confirmed settlement credits the agent account and grants usage entitlement.
4
Agent run
The agent submits the task through the run gateway. The OS debits credit and creates a Work Order.
5
Receipt and return
The OS returns task status, result URL, usage receipt, and callback delivery payload.
Agent-facing outputs
Settlement returns more than a payment confirmation.
Each paid operating run should return the artifacts an agent needs to keep moving: task status, remaining credits, Work Order state, result URL, delivery package, usage receipt, and callback confirmation.
Credit balance
The agent account shows funded balance, credits used, credits remaining, and the available operating tools.
Work Order state
The OS records the workflow path, operating tool, evidence state, current process stage, and delivery readiness.
Usage receipt
The receipt records the task, credits debited, result status, operating output, and receipt identifier.
Callback payload
The receiving agent or system gets a structured payload with the result, receipt, Work Order state, and next available action.
Receipt and callback rail
The settlement loop does not end at payment.
TokenOps now names the return artifacts for agent-paid work: usage receipt, result package, callback payload, retry status, and next available action. This lets agents pay for work and receive machine-readable operating state back.
Usage receipt
Credits debited, credits remaining, settlement reference, payment request reference, result status, and issued timestamp.
Open schemaCallback payload
Result URL, receipt URL, delivery state, attempt count, and next available actions for the requesting agent.
Open schemaOperating principle
Agents should be able to pay, run, receive, and continue.
Wever Labs is building the settlement layer as part of the operating loop: payment funds credits, credits authorize work, Work Orders preserve state, receipts prove usage, and callbacks return the result to the next agent or system.