POSSIBLE SCENARIO
Data meets compute.
A research agent could buy a specialist dataset and hire compute on demand, with a budget attached to every delegation.
When every agent can hire another, commerce needs a neutral clearing layer.
01 / THE POSSIBILITY
Imagine agents that can discover expertise, commission work and settle the outcome. A shared clearing language could make that cooperation composable.
An illustration of agents exchanging work, not a live network.
POSSIBLE SCENARIO
A research agent could buy a specialist dataset and hire compute on demand, with a budget attached to every delegation.
POSSIBLE SCENARIO
Independent services could be metered per use, with many small actions reconciled into one net settlement.
POSSIBLE SCENARIO
Agents could coordinate services around the clock, within owner-defined limits and with an auditable record.
02 / HOW IT WORKS
A mandate bounds spending; escrow reserves the agreed internal credits.
Each accepted entry links to its predecessor. Changes break the hash chain.
Allocate metered charges and fees; return unused credits under the policy.
Verify the receipt and metering chain without running a ledger.
Signed receipts and Merkle proofs make the record independently verifiable.
03 / MANY ACTIONS. ONE NET RESULT.
Verifiable metering turns many service actions into a net allocation, with signed evidence. A complementary layer above payment rails.
Rail-agnostic by design: choose the payment rail, keep the clearing evidence.
04 / WHY NOW
As agents take on actions and delegate to tools and other agents, authorization, metering and settlement need a shared language.
ILLUSTRATION / NOT TRANSACTION DATA
05 / BUILT & VERIFIED
Published protocol work at commit 54bd57f. The Stripe evidence below is from test mode.
SIGNED RECEIPT / TEST-MODE RECORD
A working state machine, independent verifier, signed mandates and Merkle proofs. Inspect the published implementation.
Explore the protocol →Stripe test collection → internal escrow → metering → net settlement → signed receipt. Independent verification returned VALID.
Read the verification record →USD 0.50 became JPY 79 gross − JPY 6 fee = JPY 73 net. The test Transfer was created; the payout step follows funds availability.
Read the test-chain evidence →06 / BUILD WITH IT
Explore the gateway request examples, read the specification and bring your own agent workflow.
curl -X POST $GW/v1/accounts \
-H "X-NeuralClear-Api-Key: $KEY" \
-d '{"account":"owner.acme","deposit":200}'
→ {"account":"owner.acme","balance":200}
curl -X POST $GW/v1/clear -d '{
"buyer_owner": "owner.acme",
"provider_url": "http://provider:8001",
"capability": "echo.text",
"payload": {"msg": "hi"}
}'
# gateway: quote → escrow hold → remote HTTP
# execution → proof → release → signed receipt
→ {"receipt_id":"rcpt_tx_…","amount":10,"fee":1}
curl -X POST $GW/v1/channels -d '{
"buyer":"owner.acme",
"provider":"agent.embedder",
"deposit":120}'
→ {"channel_id":"chan_8f58…","spendable":117}
curl -X POST $GW/v1/channels/chan_8f58…/meter -d '{
"capability":"embed.text",
"amount":1,
"payload_hash":"sha256:9f2c…"}'
→ {"sequence":42,
"prev_hash":"d31b…",
"record_hash":"77af…"}
curl -X POST $GW/v1/channels/chan_8f58…/settle
→ {"tasks_metered":100,
"net_to_provider":100,
"refunded_to_buyer":17,
"protocol_fee":3,
"chain_head":"a90c…",
"signature":"hmac-sha256:…"}
curl -X POST $GW/v1/disputes -d '{
"transaction_id":"tx_d4f0…",
"raised_by":"owner.acme",
"reason":"report never delivered"}'
# resolutions: refund | slash | split | settle
# refund moves money BACK — tested, not implied
curl $GW/v1/ledger
→ {"balances":{"owner.acme":356,
"agent.research_pro":40,
"agent.embedder":100},
"fee_pool":4,
"escrow_total":0,
"total_supply":500}
EXAMPLE / NOT LIVE
curl -X POST $GW/v1/accounts \
-H "X-NeuralClear-Api-Key: $KEY" \
-d '{"account":"owner.acme","deposit":200}'
→ {"account":"owner.acme","balance":200}
Request examples from the reference implementation. Run them against your own gateway.
07 / NEXT
2026-10-29 / TARGET
Funds are scheduled to become available at 08:00 UTC+8. Next: attempt and verify the final test payout. Completion remains subject to Stripe availability and response.
NEXT / HOSTED GATEWAY
A hosted developer gateway, with durable records and operational controls, is the next infrastructure milestone.
NEXT / DESIGN PARTNERS
Invite design partners to define a service, its budget policy and a verifiable settlement path.
Alongside these milestones: distributed persistence, execution-proof integrations and licensed custody partnerships. Current signatures authenticate records; TEE/ZK execution verification is a future integration.
Internal escrow reserves credits. Licensed partners provide real-world custody and compliance.
08 / BUILD THE NEXT LAYER
For design partners, agent-platform founders and investors: help shape the clearing layer for agent-to-agent commerce. Start with one service, one budget and one verifiable outcome.
Start a conversationOpens a public GitHub issue. Describe your use case; keep credentials, personal data and customer information private.