Skip to content

Built for the Stack

Ecosystem Compatibility

Ambr is the agreement layer — designed to integrate with the emerging AI agent commerce stack. These are ecosystem projects we're building compatibility with.

Architecture

The Five-Layer Stack

Ambr sits at Layer 2. Each layer in the stack handles a distinct concern — from discovery to payments.

Layer 1

Discovery

Agent discovery & capability exchange

Agents advertise capabilities via A2A Agent Cards and MCP Server manifests. Discovery protocols enable agents to find compatible counterparties for service agreements.

A2A Agent CardsMCP
Layer 2

Agreements

Contract negotiation, signing & management

Ambr provides the agreement layer — Ricardian Contracts that are both human-readable and machine-parsable, minted as transferable cNFTs with Principal Declarations linking agents to their legal entities.

Ambr
Layer 3

Trust

Identity verification & reputation

ZK Identity enables privacy-preserving attestation — principals prove they are verified entities without revealing identity on-chain. Zero-knowledge proofs with nullifiers prevent double-claiming while maintaining anonymity.

ZK Identity
Layer 4

Escrow

Conditional payment holding & release

KAMIYO and x0 Protocol provide escrow services with oracle-verified conditions. Funds are held until contract terms are met, with automatic release or dispute escalation.

KAMIYOx0 Protocol
Layer 5

Payments

Micropayments & session billing

x402 V2 enables HTTP-native micropayments. ACP and AP2 provide agent-to-agent payment coordination. Nevermined facilitates metered billing for compute and data services.

x402 V2ACPAP2

Integrations

Ecosystem Projects

Projects Ambr is designed to work with. Integration status reflects current development state.

x402 V2

Live

Payments Layer

Primary payment rail. Ambr functions as an x402 extension — contract hashes embedded in payment metadata. Multi-token support across Base, Solana, ACH, SEPA, and cards.

A2A Protocol

Live

Discovery Layer

Agent-to-Agent discovery and communication via JSON-RPC at getamber.dev/api/a2a, discoverable at /.well-known/agent.json.

KAMIYO

Planned

Escrow Layer

Optional escrow integration for high-value transactions. Oracle-verified quality checks and conditional payment release. Not a dependency — available when escrow is needed.

Nevermined

Planned

Payments Layer

Metered billing and session-based payment coordination for compute and data services. Python and TypeScript SDKs for integration with agent frameworks.

ZK Identity

Live

Trust Layer

Privacy-preserving identity attestation via Groth16/BN128 zk-SNARKs powered by the Demos Network. Principals prove they are verified entities without revealing which one — on-chain, only a nullifier is visible.

Purpose

Ambr's Role: The Agreement Layer

Discovery protocols help agents find each other. Trust registries verify identity. Escrow holds funds. Payment rails move money. But none of that works without a formal agreement defining the terms. That's what Ambr provides — the Ricardian Contract layer that binds the entire stack together, with human-readable terms, machine-parsable structure, and on-chain proof — each contract minted as a single NFT on Base L2 with counterparty-gated transfers and SHA-256 hash stored permanently on-chain.

Build With Us

Interested in integrating with Ambr? Get started or explore the developer docs.