ArcFX uses Agent Evidence in production.
ArcFX is an application built on top of Agent Evidence — not a component OnChainDiligence owns or operates. Its financial agent seals a real evidence bundle; OnChainDiligence verifies it independently, browser-to-browser.
ArcFX financial workflow → sealed Agent Evidence bundle → browser-local handoff → OnChainDiligence verifier → independent ArcFX signer trust lookup →
VALID / INVALID / UNVERIFIABLE
- ✓ ArcFX publishes its production Agent Evidence public signer metadata
- ✓ OnChainDiligence fetches that public metadata independently
- ✓ The evidence bundle itself is never uploaded to an OnChainDiligence verification server
- ✓ An embedded bundle key is never treated as a trust root
- — VALID does not mean the invoice or payment was approved
Developer detail: ArcFX's production signer metadata is published at arcfx-backend-production.up.railway.app/.well-known/agent-evidence-keys — the recommended path defined by the versioned Agent Evidence Interoperability Profile, which any other application can implement without ArcFX-specific knowledge.
Technocore by FLOP Labs.
Technocore proves which agent identity (a did:key) signed a statement. OnChainDiligence records how that signed evidence was used inside a Mandate → Evidence → Policy → Decision → Execution → Verification trail — it does not claim integration with the FLOP inference protocol itself.
/verify, under the Technocore tab. It runs a real Ed25519 did:key verification in your browser, not a simulation.
Space reserved for a future FLOP inference-protocol integration. Not built yet — this page will say so honestly when it changes.
tclk is currently alpha, and its reference PaperRail holds no value. OnChainDiligence captures and verifies the signed coordination transcript — it is not the settlement rail, and a verified transcript is not proof that funds moved.
Signed offer → Technocore → tclk validation → Agent Evidence →
VALID
Sequence 942 · PaperRail · Hash-lock · No real settlement
PayBox — an independent agent payment vault.
PayBox (by MoonPay) lets an agent hold and spend money under its own grant/approval rules, independently of OnChainDiligence. Neither system's decision overrides the other: an OCD ALLOW never overrides a PayBox denial, and a PayBox approval never implies OCD ALLOW.
PayBoxCommerceExecutor in the OnChainDiligence SDK implements the existing CommerceExecutor contract against PayBox's own documented pay_x402 / get_request tools — the same independent-evaluation, independent-observation lifecycle already used for the real OneSource payment, with PayBox standing in for the wallet/executor step.
This is an independent integration built against PayBox's public documentation — OnChainDiligence is not affiliated with, endorsed by, or partnered with PayBox or MoonPay. The adapter is implemented and tested (Base mainnet, USDC, one wallet credential); a live reference payment through it has not yet run.
Agent Evidence starts with
working evidence infrastructure.
The existing compliance and risk APIs are not being abandoned. They are the first production sources that return typed results and signed envelopes for financial-agent evidence.
View signed attestation — the verifiable proof
This live tool demonstrates the source layer: it returns a signed OnChainDiligence attestation. The attestation authenticates exactly what the service asserted; it does not turn the underlying provider response into objective truth.
Production APIReal observations for
financial-agent decisions.
Each API can be used independently today. In Agent Evidence, its unmodified response and trust mode can be preserved as a typed evidence record rather than flattened into an opaque log line.
Sanctions screening
Check a wallet address through the Chainalysis public sanctions oracle before funds move. The service signs the returned assertion and its own timestamp claim.
GET /screen/:address
UK company verification
Look up a UK company through Companies House: registered status and available people-with-significant-control records.
GET /company/:number
OFAC name screening
Screen a name against the public US Treasury OFAC list with confidence-scored candidate matches. It remains a screening aid, not a determination.
GET /screen-name?name=
US company verification
Resolve a US public company through SEC EDGAR by ticker, CIK or name, preserving ambiguity instead of silently selecting a filer.
GET /us-company?q=