RemitProtocol

A compliant remittance protocol for trusted AI agents.

RemitProtocol is an open, agent-native protocol layer that lets AI agents discover, quote, optimize, authorize, and execute remittances using:

• A2A (Agent2Agent) for agent interoperability and discovery via an Agent Card.
• AP2 (Agent Payments Protocol) for verifiable intent & authorization (mandates / credentials).
• x402 (HTTP 402 Payment Required) for HTTP-native micropayments (e.g., pay-per-quote, pay-per-compliance-check) when a rail or data provider requires compensation.
• ERC-8004 (Ethereum Trustless Agents compliant) for on-chain discovery + trust signals (identity, reputation, validation) when operating across organizational boundaries.

This repo is designed for agent discoverability (clear manifests, schemas, examples) and as an open-source reference you can run locally.

---

Why RemitProtocol

Remittances are not “just checkout.” They require:

• Explicit consent (no accidental sends)
• Recipient-first optimization (maximize net received)
• Auditability (who authorized what, when)
• Interoperability across agent frameworks, merchants/rails, and payment methods

RemitProtocol focuses on remittance intents and payout execution while aligning with emerging agent commerce standards.

---

Standards alignment (high-level)

A2A: Agent interoperability + discovery

• Publish an A2A Agent Card at /.well-known/agent-card.json.
• Expose A2A-compatible endpoints for message:send and optionally message:stream.

AP2: Verifiable intent & authorization

• Model remittance authorization as AP2-style mandates (verifiable digital credentials):
  • IntentMandate: what the user authorizes the agent to do
  • Checkout/CartMandate: binds final quote and recipient details
  • PaymentMandate: binds payment method/rail & final amount

x402: Micropayments for agent calls

• Optional: protect paid endpoints (e.g., quotes, sanctions checks) with HTTP 402 challenge/response.

ERC-8004: Trustless Agents (on-chain identity + reputation + validation)

• Optional: publish your agent’s identity and trust signals using ERC-8004 registries (Identity, Reputation, Validation).
• Improves discoverability and trust establishment across organizational boundaries.
• Payments are orthogonal: keep x402 for per-request payments and AP2 for verifiable mandates.

Links:

• ERC-8004 spec: https://eips.ethereum.org/EIPS/eip-8004
• 8004 community: https://www.8004.org/

---

Quickstart (GitHub Pages + discoverability)

1) Publish docs to GitHub Pages

This repo includes an MkDocs site.

• Build locally:

  pip install mkdocs mkdocs-material
  mkdocs serve

• Deploy to GitHub Pages (recommended): use the included workflow or mkdocs gh-deploy.

2) Agent discovery

Your agent card is at:

• docs/.well-known/agent-card.json (served by GitHub Pages)

If you use a custom domain (recommended), map it so agents can fetch:

• https://remitprotocol.com/.well-known/agent-card.json

---

Local reference server (optional)

A minimal FastAPI reference server is provided:

pip install fastapi uvicorn pydantic
uvicorn reference.server.app:app --reload --port 8080

Then open:

• http://localhost:8080/.well-known/agent-card.json
• http://localhost:8080/message:send (A2A HTTP+JSON binding)
• http://localhost:8080/v1/remit/quote (optional x402-protected)

---

Repository layout

remitprotocol/
├─ README.md
├─ SPECIFICATION.md
├─ mkdocs.yml
├─ docs/
│  ├─ index.md
│  ├─ quickstart.md
│  ├─ protocols.md
│  ├─ erc-8004.md
│  ├─ security.md
│  └─ .well-known/
│     └─ agent-card.json
├─ schemas/
│  ├─ remit.intent.json
│  ├─ remit.quote.json
│  ├─ remit.receipt.json
│  └─ remit.error.json
├─ openapi/
│  └─ remitprotocol.openapi.yaml
├─ examples/
│  ├─ a2a.message.send.json
│  ├─ curl.a2a.send.sh
│  ├─ curl.quote.x402.sh
│  └─ sample.ledger.jsonl
└─ reference/
   └─ server/
      └─ app.py

---

Status

• v0.1.1: Adds ERC-8004 alignment docs + agent-card tags.

---

License

Apache-2.0