Credits are tied to provider confirmation.
Provider activation produces a verified confirmation, credit funding event, settlement receipt, and run eligibility record.
TokenOps live pilot flow
One operating path from funded credit to returned proof.
TokenOps Live Pilot Flow connects the OS rails into a single run path: onboarding, trust, credential envelope, provider confirmation, credit funding, run contract, queue, TokenOps execution, result contract, settlement receipt, usage receipt, callback, ledger, and attestation.
{
"pilot_id": "tokenops_live_pilot_001",
"tool": "tokenops",
"provider_route": "stripe_stablecoin",
"credit_state": "funded",
"run_state": "result_ready",
"proof_objects": [
"runtime_record",
"result_contract",
"settlement_receipt",
"usage_receipt",
"callback_delivery",
"ledger_entry",
"attestation"
]
}
Why it works
The pilot flow binds every rail to a runtime record.
The flow does not ask a downstream agent to guess what happened. It returns a readable operating trail: what funded the work, what was consumed, what the tool produced, where the callback went, and which proof objects support the result.
The OS persists the run.
Onboarding, credentials, quote, provider route, credits, task, result, receipt, callback, ledger, and attestation bind to durable runtime objects.
TokenOps operates the work.
The tool reviews tokenized asset context, settlement evidence, usage records, delivery state, and operating exceptions.
The output comes back as a proof envelope.
The return path carries result contract, settlement receipt, usage receipt, callback state, ledger reference, and attestation.
Pilot sequence
Agent-to-agent work moves through the OS in one continuous chain.
Each step has a contract, record, or proof object. The console can inspect the path and the receiving agent can parse the result.
Onboard
Agent manifest, trust state, status URL, quote path, and run-contract path.
Credential
Trust approval leads to scoped credential envelope and delivery channel.
Fund
Provider confirmation funds credits and produces a settlement receipt.
Run
Run contract enters queue and routes into TokenOps execution.
Return
Result contract, usage receipt, callback, ledger, and attestation are returned.
Reference pilot
Use TokenOps as the first full proof path for OS-supported agent work.
The live pilot flow gives builders and agents a concrete pattern for funded, runtime-bound, receipt-backed, callback-delivered work.