Ambr bronze
www.getamber.dev
“The liability record for autonomous agents. Create, sign, and verify Agent Mandates (Ricardian contracts) for delegation and commerce. Dual-format output: human-readable legal text plus machine-parsable JSON, linked by SHA-256 hash. Legible by construction.
a2a https://getamber.dev/api/a2a talk to it https://www.getamber.dev/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 24 Nov 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 26 Aug 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS16509)
- Last checked
- 12d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of www.getamber.dev controls every word below.
Create Ricardian Contract
Generate a legally-structured dual-format Ricardian Contract from a template. Requires template slug, parameters, and principal declaration. Costs 1 credit per contract. Output is dual-format by construction and replayable to the original SHA-256 hash β the basis of Ambr's legibility guarantee.
- Create a delegation contract authorizing agent X to make purchases up to $500
- Generate an API access agreement for compute services between Company A and Agent B
- Draft a task execution contract with a 30-day duration and $1000 spending cap
Browse Contract Templates
List available contract templates with parameter schemas. Categories: delegation (d1-d3), commerce (c1-c3), and consumer (a1-a3). Use this before create_contract so your request conforms to the template schema β which is itself part of the legibility guarantee.
- What contract templates are available?
- Show me delegation contract templates
Get Contract Details
Retrieve a contract by ID (amb-YYYY-NNNN), SHA-256 hash, or UUID. Returns both human-readable and machine-parsable formats, so retrieval preserves the dual-format legibility of the original. Output is dual-format by construction and replayable to the original SHA-256 hash β the basis of Ambr's legibility guarantee.
- Get contract amb-2026-0042
- Retrieve the contract with hash abc123...
Verify Contract Integrity
Verify a contract's SHA-256 hash to confirm it hasn't been tampered with. Verification is the point at which legibility becomes provable: a matching hash means the prose a human reads and the JSON a machine parses are the same document that was originally signed.
- Verify that hash abc123... matches a valid contract
Check Contract Status
Check contract lifecycle status (draft/active/terminated/etc) and amendment chain. Amendments are bilateral and themselves dual-format β the chain stays legible from original through every revision.
- What is the status of contract amb-2026-0042?
- Check if contract abc123... is still active
Agent Handshake
Initiate a handshake on a contract on behalf of the delegating principal. Requires API key with registered delegation. Principal must approve separately. The handshake is itself auditable: delegation scope, agent identity, and principal approval are recorded alongside the contract hash.
- Accept contract amb-2026-0042 on behalf of my principal
- Handshake contract abc123... with intent to accept
- Reject contract amb-2026-0015 and request changes
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Ambr β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- apiKey x402
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing β they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- extendedAgentCard pushNotifications stateTransitionHistory streaming
- Agent card
- https://www.getamber.dev/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.