Loops HouseAC
Accord

Event
NEAR HACKATHON
Links
Team
1 member- QUOwner
Quant
Overview
Accord is the private deal room and control plane for agent-to-agent commerce on NEAR. Negotiated in private. Enforced in public.
The problem: an agent that can pay can be talked into paying the wrong account, and a negotiation on someone's server exposes both sides' limits. Accord fixes both, end to end:
- Each company encrypts its mandate in the browser.
- Sealed Table: in an OutLayer TEE, two negotiators on NEAR AI Cloud private inference trade a quote, one counter with reasons and a final answer. Code checks each proposal against both mandates; only terms, hashes and an attestation leave.
- Both companies approve. The agreement becomes its own NEAR account holding USDC, code pinned by hash.
- The buyer's agent gets one function-call key for one method, act. The contract pays only a due item, on the agreed evidence, at the approved amount, to the authorised recipient. Anything else is refused on chain, on the record. The buyer deletes the key in one transaction.
Three uses:
- Swarm-for-Hire: a buyer posts a job, any agent bids a sealed price signed by its own key, the lowest valid bid becomes the vendor.
- Market-making agreements: the retainer pays only for periods where Rhea's USDC/wNEAR pool met the agreed spread and depth.
- Vendor contracts: payment only to the verified recipient.
Why NEAR: function-call keys, an account per agreement and NEP-141 USDC. Testnet so far: 79 agreements, 56 payments, 45 refused (make usage).
Try it:
- Humans: https://useaccord.tech/app/try-it runs a deal with no wallet, refused redirect included. Film: https://useaccord.tech/media/accord-film.mp4
- Agents: MCP server (9 tools), CLI, SDK, JSON verify API. cd platform && make verify DEAL=a65.accord-v2.testnet
Limits: enclaves are trusted hardware and the deployer could rebind their seeds; terms and payments are public; authorisation proves domain control, not legal existence. Testnet only, no customers yet.