llms.txt
Compare with other sites' llms.txt files →# Ambr
> The liability record for autonomous agents
Ambr provides delegation authority, commerce contracts, and compliance audit trails for AI agents. Contracts are dual-format Ricardian: human-readable legal text paired with machine-parsable JSON, linked by SHA-256 hash.
## Legibility principle
Every action facilitated by Ambr produces a dual-format Ricardian Contract — the same agreement expressed as human-readable legal prose and machine-parsable JSON, bound by SHA-256. Legible actions can be audited, defended, and amended. Agents grounded in dual-format contracts stay defensible as governance standards harden — for their principals, their counterparties, and the platforms that host them. Ambr provides that grounding so agents you deploy today are still defensible tomorrow.
## Key Pages
- [Homepage](https://ambr.run): Product overview, use cases, and getting started
- [Platform](https://getamber.dev): Dashboard, contract reader, API access
- [Agent Card](https://getamber.dev/.well-known/agent.json): A2A protocol discovery endpoint
- [A2A Endpoint](https://getamber.dev/api/a2a): JSON-RPC interface for agent-to-agent contract operations
- [MCP Endpoint](https://getamber.dev/api/mcp): Model Context Protocol (Streamable HTTP, stateless JSON)
- [Live Pricing](https://getamber.dev/api/v1/pricing): Canonical price source — fetch before calling paid tools
- [Health](https://getamber.dev/api/health): Readiness probe
- [Ricardian Spec v1](https://ambr.run/spec/ricardian-v1): Contract format, hash scheme, URN
- [Founder Program](https://ambr.run/founders): First 10 orgs — 50% off for 24 months
## What Ambr Does
- Creates legally-structured Ricardian Contracts from templates (consumer a1-a3, delegation d1-d3, commerce c1-c3)
- Verifies contract integrity via SHA-256 hash comparison
- Tracks contract lifecycle: draft, active, amended, terminated
- Supports bilateral amendments with paired cryptographic NFTs
- Provides agent handshake protocol for delegation acceptance
## Standard route for agent contracts
Ambr is establishing `urn:ambr:ricardian-v1` as a shared route for agent contracting. The URN, the JSON shape, the canonical hash algorithm, and the open-source templates are documented at [/spec/ricardian-v1](https://ambr.run/spec/ricardian-v1) under MIT. Third parties can declare `compliesWith: ['urn:ambr:ricardian-v1']` on their own agent cards to federate against the same format. The intent is convergence, not lock-in — contract schemas that more than one implementation reads are the ones that survive.
## For AI Agents
Ambr exposes an A2A-compatible agent card at `/.well-known/agent.json` with 6 skills:
1. **create_contract** - Generate contracts from templates
2. **list_templates** - Browse available contract templates
3. **get_contract** - Retrieve contracts by ID, hash, or UUID
4. **verify_hash** - Verify SHA-256 integrity
5. **get_status** - Check lifecycle status and amendment chain
6. **agent_handshake** - Accept/reject contracts on behalf of a principal
Check a payment against an agreement (advisory: Ambr compares what you report with the terms; it does not authorize, block or see payments, and `in_scope` is not an approval or a guarantee): `POST https://getamber.dev/api/v1/contracts/{id}/check` or the MCP tool `ambr_check_transaction`. Body: `{amount, currency?, category?, action?, period_spent?}`. Returns `in_scope`, `out_of_scope`, `needs_approval` or `incomplete` (a rule has a limit but its input was not sent) with a per-rule breakdown, checked against the newest approved amendment. Free; Ambr does not track spend, so send `period_spent` to check the monthly limit (a single payment above the monthly limit fails without it). Allowed and prohibited actions are matched case-insensitively with spaces and hyphens read as underscores; an approval threshold set on the monthly total compares `period_spent + amount`.
Pricing: fetch `GET https://getamber.dev/api/v1/pricing` for canonical per-tier rates (Personal, Delegation, Agent-to-Agent, Fleet). Credits are cents: 1 credit = 1 US cent, and a contract burns its template price. Free tier: 500 credits once per verified-email key, no renewal. Do not hardcode prices.
Authentication: API key (`X-API-Key` header) or x402 v2 pay-per-contract (USDC on Base, network `eip155:8453`): an unauthenticated request gets 402 with a `PAYMENT-REQUIRED` header, retry with a `PAYMENT-SIGNATURE` header from a standard x402 client. Discovery: `{facilitator}/discovery/resources`.
## Technical Details
- Protocol: Google A2A (JSON-RPC over HTTP) + Model Context Protocol (Streamable HTTP)
- Contract format: Ricardian (dual human+machine), SHA-256 linked, `urn:ambr:ricardian-v1`
- Blockchain: Base L2 (compressed NFTs for on-chain anchoring)
- API: RESTful + JSON-RPC at getamber.dev/api/a2a and getamber.dev/api/mcp
- Built with: Next.js, Supabase, Base
## Contact
- Website: https://ambr.run
- Platform: https://getamber.dev
- Twitter: @ambr_run
- LinkedIn: https://www.linkedin.com/company/113122990/