References

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

Source code

01 Accord repository Contracts, enclave jobs, SDK, MCP server, CLI, app and this website. MIT licence. github.com/Adityaakr/accord
02 Claims and their limits The source of truth for every claim on this site. platform/GOAL.md
03 Interfaces Every method, event, error, job schema, SDK call, MCP tool and CLI command. platform/INTERFACES.md
04 MCP server, SDK and CLI @accord/mcp, @accord/sdk and accord; run from a clone, not published to npm. platform/packages

Official references

01 NEAR access keys A function-call key is limited to one receiver and a list of methods, cannot attach a deposit, and spends gas from a fixed allowance. docs.near.org
02 NEAR asynchronous cross-contract calls docs.near.org
03 NEAR AI Cloud private inference docs.near.ai
04 OutLayer trust and verification How a run's attestation is checked with outlayer-verify. app.outlayer.ai
05 Kraken public order book docs.kraken.com
06 Kraken account-specific execution data docs.kraken.com

The exchange references illustrate the difference between aggregate and account-specific evidence; they do not assert that Accord has integrated Kraken.

NEAR standards used

01 NEP-591 global contracts A contract referenced by its code hash cannot change; the basis for pinning each agreement's code. github.com/near/NEPs
02 NEP-141 fungible tokens ft_transfer and ft_transfer_call, including refunds of unused amounts. github.com/near/NEPs
03 NEP-145 storage management github.com/near/NEPs
04 NEP-297 events github.com/near/NEPs
05 NEP-366 meta transactions docs.near.org
06 NEP-413 message signing github.com/near/NEPs
07 Gas and storage docs.near.org
08 RPC providers docs.near.org

OutLayer and NEAR AI Cloud

OutLayer

01 NEAR integration app.outlayer.ai
02 Secrets app.outlayer.ai
03 Signing keys app.outlayer.ai
04 TEE attestation app.outlayer.ai
05 outlayer-verify github.com/out-layer

NEAR AI Cloud

01 Verification Attestation reports fetched with a fresh nonce, and per-response signatures bound to the attested model key. docs.near.ai
02 Gateway attestation docs.near.ai
03 Model attestations docs.near.ai
04 Response signatures docs.near.ai
05 End-to-end encryption docs.near.ai

Primary sources

01 FBI IC3, Internet Crime Report 2025 Business email compromise: $3,046,598,558 across 24,768 complaints. ic3.gov
02 OWASP Top 10 for LLM Applications, LLM01:2025 Prompt injection is the first risk, including indirect injection from external sources. genai.owasp.org
03 UK NCSC, Prompt injection is not SQL injection Design protections should focus on deterministic (non-LLM) safeguards that constrain the system's actions. ncsc.gov.uk
04 NEAR Intents confidential execution It does not hide data an application publishes or an ordinary transfer on the destination chain; the reason Accord makes no claim of private settlement. intents.near.org

On this page

Source code
Official references
NEAR standards used
OutLayer and NEAR AI Cloud
Primary sources

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.