Trusted execution 402-native payments Fiduciary optimization ERC-8004 Trustless Agents interoperable

A compliant remittance protocol for trusted AI agents.

RemitProtocol enables agents to quote, optimize net delivery, and execute payouts with explicit consent and auditability — interoperable with ERC-8004 Trustless Agents.

Stage → Confirm
No accidental sends
Deterministic
Auditable logic
$0.01 fee
Cheapest ever
Protocol alignment

Interoperable with agent-commerce standards

RemitProtocol complements interoperability and payment standards by specializing in remittance intent, consent, and payout execution.

A2A interoperability
Agent discovery and messaging
x402 micropayments
Optional HTTP 402 payments
ERC‑8004 Trustless Agents
Identity + reputation + validation

*This site describes a protocol + reference implementation. It is not a bank, custodian, or money transmitter.

Telegram Agent Demo
USD → KES → M‑Pesa
Live-ready
9:41
Back
RemitProtocol Agent
last seen recently
Send 10,000 KES to Mom.
3:19 PM
RemitProtocol Agent
To net 10,000 cash, send 10,115 KES (includes 115 MP KES withdrawal fee).
3:19 PM ✓✓
RemitProtocol Agent
Top up $78.50 and confirm to execute (fee $0.01).
3:19 PM ✓✓
/send $78.50 to Mom
3:20 PM
RemitProtocol Agent
Staged: 10,115 KES → Mom (+2547•••). Reply /confirm 1234 to execute. /cancel to abort.
3:20 PM ✓✓
/confirm 1234
3:21 PM
RemitProtocol Agent
Executed ✅ Tracking ID: rp_7f3a… Ledger updated.
3:21 PM ✓✓
Celebration gif
3:21 PM ✓✓
Message
Why RemitProtocol

Net delivery comparison

What your recipient actually receives after all fees — the only number that matters.

Provider Send €100 Exchange Rate Transfer Fee M‑Pesa Withdrawal Fee Net Received (KES)
RemitProtocol €100 148.2 €0.01 KES 33* KES 14,786
Wise €100 147.8 €1.20 KES 105 KES 14,485
Remitly €100 145.5 €1.99 KES 105 KES 14,155
WorldRemit €100 143.9 €2.99 KES 105 KES 13,850

*RemitProtocol optimizes send amount to land within lowest M‑Pesa withdrawal tier. Rates illustrative.

How it works

A five-step protocol flow for agent-native remittance

Design for intent, consent, and proof. Separate reasoning from execution. Keep everything auditable.

01

Discover

Agent reads capabilities (corridors, limits, rails) and resolves recipient identity.

02

Quote

Fetch rates/fees; compute net delivered; produce an auditable quote object.

03

Optimize

Apply fiduciary rules (tier thresholds, fee jumps) to recommend the best delivery plan.

04

Authorize

User confirms intent (explicit consent). Agent request is signed and replay-protected.

05

Execute

Perform payout via configured rails. Return tracking ID + receipt + ledger entry.

Core primitives
RemittanceIntent (who, how much, corridor, constraints)
Quote (rates, fees, expiry, net delivered)
OptimizationResult (tier-aware recommendation)
Authorization (explicit user consent + signature)
Receipt (tracking id, ledger hash, timestamps)
Guardrails by default
Stage → confirm → execute (two-step commit)
Circuit breakers (max amount, corridor allowlist)
Backend-only API payload construction
Immutable append-only audit log
Replay protection + request integrity
Demo-ready MVP

A crisp demo that proves the thesis

Show the protocol primitives, then show the payout. Keep it simple. Make it auditable.

1) Fiduciary recommendation — Trigger tier-optimization and explain why the agent recommends rounding or splitting.
2) Stage transfer — Show a structured staged summary (recipient, amount, constraints, and receipt preview).
3) Confirm & execute — Require explicit confirmation. Execute payout and return a tracking ID + ledger entry.
How it works

From intent to delivery in four steps

The protocol handles routing, optimization, and execution — you just say what you want.

1

You speak

“Send 5000 KES to Mom” via Telegram.

2

Agent reasons

Resolves contact, checks tiers, produces a staged intent + quote.

3

You confirm

Review breakdown + confirm with PIN. No confirmation = no transfer.

4

Money arrives

M‑Pesa payout executes. Recipient receives KES with a tracking ID.

Security & compliance posture

Built for explicit consent, auditability, and trust

We separate agent reasoning from execution, require explicit user authorization, and record all critical actions.

Explicit consent

No money moves without an explicit confirmation step.

Two-step commit: stage → confirm with PIN
Agent proposes, human disposes — never auto-executes
Session timeout: unconfirmed transfers expire

Full audit trail

Every action is logged immutably — no silent failures.

Append-only JSONL ledger for all transfer events
Timestamps + redaction (no PINs, no full numbers)
Exportable receipts and summaries

Hard guardrails

Circuit breakers that cannot be overridden by the AI.

Max transfer limit enforced in code
Single authorized user (demo mode)
Reasoning separated from execution
Open source

Trust through transparency

Protocol primitives, schemas, and reference implementation are open for audit.

Protocol alignment

Designed to interoperate with emerging agent-commerce standards

RemitProtocol complements commerce and payment protocols by specializing in remittance intents, compliance guardrails, and payout execution across rails.

A2A / Agent2Agent
A2A-compatible agent interoperability
Well-known agent card discovery
Interoperable message parts
Works across agent frameworks
x402 / 402 Payment Required
HTTP-native micropayment primitives
Pay-per-request economics
Machine-first settlement handshake
High-frequency, low-value calls
AP2-aligned mandates
Verifiable authorization artifacts
Explicit authorization boundaries
Deterministic, auditable receipts
Separation of reasoning and execution
/.well-known patterns
Discovery & capability manifests
Agent-readable capability discovery
Extensible corridor/rail metadata
Versioned manifests
ERC‑8004 (Ethereum)
Trustless Agents interoperability
Identity registry (ERC‑721 + registration file)
Reputation signals & validation hooks
Complements A2A + AP2 + x402
Positioning

Commerce protocols solve buying. RemitProtocol solves compliant remittance execution and recipient-first optimization.

Contact

Request a demo or join the waitlist

We’ll share a one‑pager, demo script, and the live Telegram walkthrough.