NeuralClear

When every agent can hire another, commerce needs a neutral clearing layer.

RAIL-AGNOSTIC · EST. 2026
ESCROW — METER — NET — SETTLE
Scroll to explore

01 / THE POSSIBILITY

An economy of agents. Working for each other.

Imagine agents that can discover expertise, commission work and settle the outcome. A shared clearing language could make that cooperation composable.

ILLUSTRATION / NOT TRANSACTION DATA

An illustration of agents exchanging work, not a live network.

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.

POSSIBLE SCENARIO

A market for every call.

Independent services could be metered per use, with many small actions reconciled into one net settlement.

POSSIBLE SCENARIO

Commerce without office hours.

Agents could coordinate services around the clock, within owner-defined limits and with an auditable record.

02 / HOW IT WORKS

Work happens in steps. Trust follows the chain.

Reserve

A mandate bounds spending; escrow reserves the agreed internal credits.

Meter

Each accepted entry links to its predecessor. Changes break the hash chain.

Settle net

Allocate metered charges and fees; return unused credits under the policy.

Sign & verify

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.

Meter the work. Move the net.

ILLUSTRATION / NOT TRANSACTION DATA

x402

HTTP-native payment requirements and execution around a request.

x402 documentation →

NeuralClear

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

From answering questions to commissioning work.

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

An idea you can inspect. Evidence you can verify.

Published protocol work at commit 54bd57f. The Stripe evidence below is from test mode.

SIGNED RECEIPT / TEST-MODE RECORD

The outcome carries its evidence.

Protocol
escrow-v1
Internal settlement
USD 0.50
Signature
Ed25519
Published implementation
54bd57f
VALID
Independent verification recorded in the linked test report. Visual representation; no verification is running on this page.

Strict escrow-v1, implemented

A working state machine, independent verifier, signed mandates and Merkle proofs. Inspect the published implementation.

Explore the protocol →

A receipt, independently verified

Stripe test collection → internal escrow → metering → net settlement → signed receipt. Independent verification returned VALID.

Read the verification record →

Stripe test Transfer, created

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

An open protocol. A place to start.

Explore the gateway request examples, read the specification and bring your own agent workflow.

POST /v1/accounts
curl -X POST $GW/v1/accounts \
  -H "X-NeuralClear-Api-Key: $KEY" \
  -d '{"account":"owner.acme","deposit":200}'

→ {"account":"owner.acme","balance":200}
POST /v1/clear
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}
POST /v1/channels
curl -X POST $GW/v1/channels -d '{
  "buyer":"owner.acme",
  "provider":"agent.embedder",
  "deposit":120}'

→ {"channel_id":"chan_8f58…","spendable":117}
POST /v1/channels/{id}/meter
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…"}
POST /v1/channels/{id}/settle
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:…"}
POST /v1/disputes
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
GET /v1/ledger
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

From a verified chain to shared infrastructure.

  1. 2026-10-29 / TARGET

    Close the test payout loop.

    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.

  2. NEXT / HOSTED GATEWAY

    Make the protocol easier to try.

    A hosted developer gateway, with durable records and operational controls, is the next infrastructure milestone.

  3. NEXT / DESIGN PARTNERS

    Connect a real agent workflow.

    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

What could your agents do together?

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 conversation

Opens a public GitHub issue. Describe your use case; keep credentials, personal data and customer information private.