Pilot quickstart

Add OnChainDiligence to one existing payment flow.

Keep your wallet. Keep your payment provider. Add OCD once. A pilot uses one existing, low-value agent payment and ends with a signed receipt you can verify yourself.

What OCD does

OnChainDiligence is an independent evidence layer around autonomous-agent payments:

Before payment, it checks the proposed payment against the policy you supply and returns ALLOW, REQUIRE_APPROVAL or BLOCK, with a signed preflight receipt.
After payment, it independently reads the chain to see what actually settled, and issues a signed receipt that keeps the policy decision, the execution and the settlement as separate statements.

OCD does not hold wallet keys, authorize spending, execute payments, guarantee safety or compliance, detect fraud, or prove that a merchant delivered a service. It works alongside whichever executor you already use.

Where it sits in a payment flow

01Agent proposes a payment
02OCD checks it against your policy
03Your wallet or executor authorizes and pays
04OCD independently observes what settled
05A signed receipt records the evidence

What you send OCD

The proposed payment: network, asset, amount, recipient, and optionally the resource URL and paying wallet — public values only.
Your policy: for example a maximum amount, allowed networks and assets, and an expected recipient.
After your executor pays: the transaction hash.
Optionally, what your payment provider reported, recorded as a provider claim (see provider evidence).

Never send private keys, seed phrases, API secrets, signing credentials, payment authorizations, or private URL parameters. OCD never needs them.

What OCD returns

Stage	You receive
Preflight	A decision (`ALLOW` / `REQUIRE_APPROVAL` / `BLOCK`) with reasons, and a signed preflight receipt.
After payment	A signed receipt with settlement `CONFIRMED`, `NOT_CONFIRMED` or `UNVERIFIED`, the exact preflight-versus-observation checks, and a stated binding strength.
Verification	`VALID`, `INVALID` or `UNVERIFIABLE` — online, or offline with OCD’s published keys.

VALID means the receipt is intact and was signed by OCD under the verifier contract. It is not payment authorization, service delivery, safety or compliance.

What stays under your control

Your wallet or payment provider keeps the keys, signs, submits, and applies its own approval rules. An OCD ALLOW is a policy opinion, never an authorization to spend: your executor still independently decides whether to pay, and OCD never overrides it.

Supported today

Independent settlement observation for USDC on Base and Ethereum, pathUSD on Tempo, and USDC on Solana.
SDK executor adapters for x402, PayBox, Turnkey, Crossmint, Coinbase CDP and Circle, or your own signer.

Easiest integration routes

1. Start with a payment that already happened

No integration at all: send a supported transaction reference and get a signed observation-only receipt. Its decision is UNKNOWN, because OCD did not check anything before that payment.

curl -s -X POST https://mcp.onchaindiligence.com/observe-payment \
  -H "Content-Type: application/json" \
  -d '{"network":"eip155:8453","transaction_hash":"0x…"}'

2. TypeScript: the Commerce SDK

The shortest full lifecycle for Node.js. See the autonomous payment reference for the complete walk-through.

npm install @onchaindiligence/sdk @x402/core @x402/evm @x402/fetch

3. Any language: HTTP

Open an operation, preflight, register the execution, pay with your own executor, then finalize with the transaction hash:

POST /operations                                   → operation_id, recovery_credential
POST /x402/lifecycle/preflight-payment             → decision, signed preflight receipt, finalization capability
POST /operations/:id/execution-bindings            → durable execution identity (before you pay)
     …your own wallet or provider pays…
POST /operations/:id/finalize                      → signed receipt from OCD's own chain observation

Base URL: https://mcp.onchaindiligence.com. The preflight costs $0.01, paid with standard x402; observation-only receipts and receipt verification are free. The recovery_credential and finalization capability are OCD-issued operational secrets: keep them server-side, never in browser storage, receipts or logs.

What a pilot looks like

Pick one existing, low-value payment your agent already makes.
Run an OCD preflight before it, with your policy.
Pay exactly as you do today, with your own executor.
Finalize with the transaction hash and receive the signed receipt.
Verify the receipt, and tell us whether the evidence was useful.

To plan it, we only need: your executor or payment provider, the network and asset, your language or runtime, the payment flow you want to use, whether you receive a transaction hash, and whether your provider emits its own evidence. We will never ask for keys or credentials.

Contact

Email support@onchaindiligence.com with the subject “pilot”. We are happy to work entirely asynchronously.