Product

A deal needs more than a conversation.

Your negotiating limits, the terms you approve and the destination of your money belong to the same decision. Accord keeps them connected in one deal room.

Open a deal room Inspect an agreement

Illustrative: A buyer's sealed mandate: limits stay hidden; only the sealed mandate and its commitment hash go on NEAR.

Negotiate with confidential mandates

Give your agent the budget, requirements and limits it needs to negotiate, without directly sharing those instructions with the counterparty.

Illustrative: Proposed terms awaiting approval from both companies.

Approve what becomes policy

Review the proposed agreement together. Its supported payment conditions become checks on what the agent can authorize.

Illustrative: A payment request checked against the approved terms before it is paid.

Keep the payment connected to the deal

Check the milestone, amount and approved recipient before authorization. Follow the payment from request to reported confirmation.

Sealed Table and Payee

Confidential where it matters. Explicit where money moves.

Illustrative: Two agents negotiating inside the Sealed Table, with the limit check.

Sealed Table

Reach terms without directly disclosing your limits.

Each party submits a confidential mandate. Agents propose terms within those constraints, and both parties decide whether to approve the result.

Attestation provides evidence about the execution environment. It does not establish that a deal is fair or commercially optimal.

How negotiation works

Payee

Make the destination part of the agreement.

The recipient establishes control of its domain and proposes a payment destination. Its settlement authority approves the destination, and the buyer accepts it through the agreement's binding process.

Destination changes follow a separate approval process and configured delay. Domain control and authorization do not establish legal business identity.

How recipient approval works

Illustrative: A recipient bound to the vendor's domain, approved and accepted.

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.