# OnChainDiligence OnChainDiligence is an independent reconciliation layer for autonomous-agent payments. Before a payment, it records the declared action and checks it against caller-supplied policy. The caller's own wallet or executor authorizes and submits the payment; OnChainDiligence never holds wallet keys and never executes payments. Afterward, it independently observes what settled on-chain, reconciles it against what was declared and what the executor reported (executor and merchant claims stay separate from settlement), and issues a signed, independently verifiable receipt. This is a convenience index of owned public resources, not a trust root. The application-owned agent profile below is not an industry standard. ## Product - How it works: https://onchaindiligence.com/#how-it-works - Documentation: https://onchaindiligence.com/docs - Pilot quickstart: https://onchaindiligence.com/pilot - Autonomous payment reference: https://onchaindiligence.com/docs/autonomous-payment-reference - Provider evidence: https://onchaindiligence.com/docs/provider-evidence - Receipt Explorer: https://onchaindiligence.com/receipt - Integrations hub: https://onchaindiligence.com/integrations - Auto-Evidence v1: a local stdio MCP proxy for one upstream MCP server. Each economic tool must be registered in a strict descriptor (exact amount, network, asset and recipient plus a stable purchase-attempt ID in the arguments; transaction reference in the result); ordinary tools pass through unchanged. OCD records and policy-checks the declared payment, the upstream executor pays, then OCD observes supported settlement and reconciles. Not published to npm yet; not automatic for arbitrary tools; no global exactly-once, fulfilment or agent-identity claim. https://onchaindiligence.com/developers#auto-evidence - Reconciliation Ledger v1 (live, authenticated workspace): groups payment activity as Accounted for, Needs attention or Pending, with one reason per item, and links each item to its underlying evidence. These are operational summaries of the evidence OCD currently holds, not verdicts on authorization, delivery, safety or compliance; counts cover the current source page, not workspace totals. https://app.onchaindiligence.com/#reconciliation | Docs: https://onchaindiligence.com/docs#reconciliation-ledger - Wallet Evidence: authenticated, user-initiated, read-only recent payment-asset activity for a connected EVM wallet or pasted address on Base (USDC), Tempo (pathUSD) and Arc (USDC), with exact network and transaction-hash correlation to evidence in the authenticated workspace. Classifications: Agent-linked, OCD-linked, Saved receipt, Unlinked; unlinked activity remains Unlinked. History is bounded and complete only within the stated block range (on Arc, the user can explicitly search earlier bounded history; nothing is crawled automatically). The chain read is live and not signed. Optional read-only wallet-control proof is separate from chain evidence and is not ownership, identity, authorization or agent identity. No portfolio or pricing; viewing activity remains read-only. A separate, explicit Create signed receipt action on a supported transaction creates or returns a signed observation-only receipt (policy UNKNOWN); it does not need wallet-control proof, and an Unlinked transfer stays Unlinked alongside that receipt. https://app.onchaindiligence.com/#wallet-evidence | Docs: https://onchaindiligence.com/docs#wallet-evidence ## Free HTTP capability: receipt for a past payment - POST https://mcp.onchaindiligence.com/observe-payment with {"network", "transaction_hash"} for a supported stablecoin payment on Base, Ethereum, Tempo, Arc (eip155:5042, native USDC system Transfer stream, 18 decimals, finalized head) or Solana. The website, the API, Wallet Evidence and the public MCP tool create_payment_receipt can create or reuse these observation-only receipts for completed supported payments; none of them executes payments. - OnChainDiligence independently observes the transaction and returns a signed observation-only receipt. Its decision is UNKNOWN: it does not claim the payment was authorized. - Receipts are unlisted, not private: anyone with the exact receipt ID can retrieve them. - Web page (no code needed): https://onchaindiligence.com/create-receipt - Docs: https://onchaindiligence.com/docs#observe-payment ## Agent interfaces - Agent instructions (concise operating guide for AI/coding agents): https://onchaindiligence.com/skill.md - Available in Claude through the Claude Marketplace: https://claude.com/marketplace/connectors/onchaindiligence - Public MCP (free: inspect_payment, get_receipt, verify_receipt, create_payment_receipt): https://mcp.onchaindiligence.com/public/mcp - A2A Agent Card: https://mcp.onchaindiligence.com/.well-known/agent-card.json - A2A 1.0 / JSON-RPC endpoint: https://mcp.onchaindiligence.com/a2a - A2A has exactly three advertised skills: inspect-payment, get-receipt, verify-receipt (inspect / retrieve / verify). Public MCP has four tools (inspect / retrieve / verify / create observation receipt). A2A v1 does not expose receipt creation, payment execution, wallet signing, private/workspace tools, paid x402 tools or agent provenance mutation; it does not authorize spending. - MCP endpoint (paid x402 tools): https://mcp.onchaindiligence.com/mcp - MCP registry ID: com.onchaindiligence/compliance - Agent profile: https://onchaindiligence.com/agents/profile.json - Agent Evidence Explorer: https://onchaindiligence.com/agents - Agent Evidence verifier: https://onchaindiligence.com/verify ## Developer resources - Developer quick-start: https://onchaindiligence.com/developers#mcp - Agent Evidence protocol and source: https://github.com/Qazza1/onchaindiligence - TypeScript SDK: https://github.com/Qazza1/onchaindiligence-sdk - Agent Evidence package: https://www.npmjs.com/package/@onchaindiligence/agent-evidence ## Trust boundaries - A VALID receipt proves integrity and authenticity under the verifier contract only, not payment authorization, service delivery, safety or compliance. - Provider or executor claims are recorded separately from independent settlement observation. - A Technocore DID signature proves that a key signed exact bytes, not truth or real-world identity. - Registry entries and DID notes are discovery hints, not trust roots. - A2A caller/client identity assertions do not establish agent provenance, wallet ownership or who made a payment. Missing evidence is not a contradiction; a Signed Payment Claim is not an OCD Receipt. - tclk/1 coordination does not prove payment settlement or delivery.