Verify

Verify an agreement.

Check any Accord agreement from public data. No account, no keys.

Live from testnet 5 of 5 ok

01 Agreement a6.accord-v2.testnet · by accord-v2.testnet ok
02 Contract code Release 3 · 8wMuMRre… ok
03 Access keys None; the agent is revoked ok
04 Recipient halcyon-mm.testnet · v1 proof ok
05 Record Executing · 16.50 of 35.50 paid · 1 refusal ok

Sealed outcome, model attestation and release attestation are checked by make verify and in the app. Open in the app The command

Full check · make verify

make verify DEAL=a6.accord-v2.testnet

01 Contract code Matches the published release ok
02 Agreement keys No full-access key ok
03 Sealed outcome Signed inside the enclave ok
04 Enclave release Needs the outlayer-verify tool not checked
05 Model attestation The real model, fresh nonce ok
06 Recipient Proven on the vendor's domain ok
07 Record Payments match the receipts ok

6 of 7 ok a6.accord-v2.testnet Show raw output accord verify · a6.accord-v2.testnet code code hash 8wMuMRre… = release 3 (global by hash) · no deploy method · ok keys 0 key · none · no full access · ok sealed outcome signature ok · commitments match · agreement matches · ok release sealed-table wasm 7c832ce9… · keys from pubkey run 13682 · … · not checked model z-ai/glm-5.3-flash · fresh nonce 9debe4c3… · nonce bound in the report · ok payee halcyon-mm.testnet · proof accordweb-production.up.railway.app signed by the release's payee key · ok record 1 payments · 1 refusals · 0 exceptions · receipts match paid · ok verify: 6 checks ok · 1 not checked

Pages

Home: What Accord is and what it is built on, the six agreement types, market-making agreements, how a deal room works in six steps, the seven core controls, use cases, why now, the demonstration, privacy, research and FAQ.

Market-making agreements: Retainers tied to agreed liquidity conditions; scheduled observations decide whether each payment is eligible.

Product: Negotiation, approval and payment in one deal room.

Sealed Table: Confidential negotiation between agents inside an attested enclave.

Payee: Recipient authorisation: domain proof, settlement authority approval and buyer acceptance.

Security: Claims and their limits, custody per piece, the privacy boundary and where each attack stops.

Research: Every source behind Accord's design: what each establishes, what it does not, and the decision it informs.

Documentation: The docs overview: what Accord is, and every docs page by section.

Docs: Quickstart: Run one deal on NEAR testnet at /app/try-it in about 3 minutes: sign in, get test funds, seal your limits, let the demo agent pay, watch a redirect get refused, and revoke the key.

Docs: Concepts: The agreement's states, the parts of Accord, the agent's one scoped key, and the refusal codes the contract records instead of panicking.

Docs: Agreement types: Six agreement types share the same controls; the commercial fields and the evidence accepted change. Two are built and shown in the demonstration, four are planned.

Docs: How it works on NEAR: The factory and agreement contracts, the three OutLayer enclave jobs, NEAR AI Cloud's attestations, USDC held by each agreement's own account, and the relayer that never carries act.

Docs: Verify an agreement: Check any Accord agreement from public data with one command and no keys, or run five of the checks in the browser at /verify.

Docs: CLI and commands: Every make target a reader runs, what it does, the transaction where agreement a6 ran it on testnet, and real output from the platform README.

Docs: Contracts and endpoints: The accounts and endpoints Accord uses on NEAR testnet, and the agreement contract's change and view methods, one line each.

Docs: Security and limits: The six claims Accord makes, each with its limit, what NEAR does not do here yet, the limits of this testnet deployment, and the threat model.

Docs: References: The official documentation behind each part of Accord, the NEAR standards it uses, and the primary sources for the problem it addresses.

Verify an agreement: Walk the attestation chain of an agreement, step by step.

Try to move the money: The open demonstration inbox: send the agent an attack and watch the contract refuse it.

How to start: Sign in with a NEAR wallet, choose a workspace, create a deal room and invite the counterparty, on NEAR testnet.

Public record: Agreements, payments and refusals from the Accord demonstration, each refusal with its recorded reason.

Contact: Get in touch with the Accord team.

Privacy: What this site stores and for how long.