Network / public evidence context

A record worth sharing.
A context worth knowing.

Understand who participated, which action was recorded, and how to verify the evidence independently.

Evidence profilesAction profilesIntegrationsVerification surfaces

A curated view of published capabilities and existing references. Profiles are informational; they do not certify identity, safety, or service delivery.

Evidence profiles

Who contributes to
the evidence lifecycle?

Evidence profile

OnChainDiligence

https://onchaindiligence.com
Evidence / receipt issuer

Capabilities

  • Commerce Lifecycle v1: payment preflight, observation and reconciliation
  • Signed Action Receipts and Agent Evidence bundles
  • Base / USDC commerce reference; support depends on the execution interface

Evidence source types

Configured policy evaluation, executor claims, independent chain observations and explicitly attributed caller reports. Coverage depends on the record.

This profile describes published capabilities. It is not an identity attestation or an endorsement. Receipt proof must be verified for each artifact.

Evidence profile

ArcFX

https://www.arcfx.app
Reference / live integration

Capabilities

  • Financial-agent workflow producing sealed Agent Evidence
  • Browser-local evidence handoff to OnChainDiligence
  • Public production signer metadata used as an independent trust source

Evidence source types

ArcFX supplies the sealed bundle through the existing browser handoff. The verifier obtains public signer metadata separately. See the integration walkthrough for the precise trust boundary.

ArcFX is independently operated. This page does not imply a commercial partnership, publish private invoice data, or invent a receipt count. No shared public ArcFX receipt is asserted here; use the existing handoff. A VALID bundle does not mean an invoice was approved or paid.

Action profiles

Start with commerce.

Current payment workflow

Commerce Lifecycle v1

Mandate → Evidence → Policy → Decision → Execution → Observation / Reconciliation → Verifiable Action Receipt.

Commerce developer guide →
Public artifact

Action Receipt

Decision, execution, settlement and proof are distinct facts. Missing or unverified evidence stays explicit.

Open the receipt explorer →
Evidence format

Agent Evidence v0

The published bundle format and verification contract underpin portable evidence. It is distinct from the commerce lifecycle interface.

Read the protocol →

Payments are our first consequential action, not our definition of consequential action. Additional action profiles are not presented as shipped.

Integrations

Explicit roles.
Documented boundaries.

ChatGPT / public MCP

Submitted · review pending

Developer Mode host-loop passed. Free inspection, public receipt lookup and verification; no paid MCP capability exposed.

Claude Custom Connector

Validated

Connect the free public MCP endpoint. Inspect a proposal or retrieve and verify an existing receipt.

Execution & evidence sources

Documented integrations

ArcFX reference integration, x402, PayBox compatibility and Technocore signed-message evidence. Read each integration's scope; no partnership is implied.

Verification surfaces

Let the next reader
check for themselves.

Public receipt

Open an exact receipt ID. The browser checks its proof against the public key registry.

Explore →

Evidence bundle

Inspect the bundle and trust context in your browser, including the existing ArcFX handoff.

Verify →

Offline SDK verification

Use the published SDKs with explicit trust material to independently verify a supported artifact offline.

SDK packages →

VALID / INVALID / UNVERIFIABLE describe proof verification. VALID does not automatically mean the action succeeded, was safe or compliant, or delivered a service.