Ambr
v0.3.0Ricardian contracts for AI agents — dual-format, SHA-256 bound, legible by construction.
Endpoint health
online- Last checked
- 11/20/2026, 4:16:59 AM
- Latency
- 220 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.getambr%2Fambr-mcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.getambr/ambr-mcp-server": {
"url": "https://getamber.dev/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
ambr_agent_handshake
Initiate a handshake on a contract on behalf of your delegating principal. Requires an API key with an active delegation (principal wallet registered via /api/v1/delegations). Records the agent's intent to accept, reject, or request changes on the contract. The principal must separately approve via wallet signature on the Reader Portal. Args: - contract_id (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID - intent (string, required): "accept" | "reject" | "request_changes" - message (string, optional): Note for the counterparty - visibility_preference (string, optional): "private" | "metadata_only" | "public" | "encrypted" Returns: Handshake status and next steps for principal approval. Legibility: the handshake itself is auditable — delegation scope, agent identity, and principal approval are recorded alongside the contract hash.
Schema valid · SHA-256 e7616fa98310…
View input schema
{ "type": "object", "properties": { "contract_id": { "type": "string", "description": "Contract ID, SHA-256 hash, or UUID" }, "intent": { "type": "string", "enum": [ "accept", "reject", "request_changes" ], "description": "Handshake intent" }, "message": { "type": "string", "description": "Optional note for counterparty" }, "visibility_preference": { "type": "string", "enum": [ "private", "metadata_only", "public", "encrypted" ], "description": "Optional visibility preference for negotiation" } }, "required": [ "contract_id", "intent" ] }ambr_check_transaction
Check one payment against the limits of an agreement. Advisory only: Ambr compares what you report with the figures stored with the agreement; it does not authorize, block or see the payments it checks, and a "within_limits" answer is not an approval or a guarantee. It checks only what a program can check exactly: status, validity window, currency, per-transaction and monthly limits, a total budget, a price or monthly fee, the approval and escalation thresholds, and the category and action labels you send, matched exactly against the agreement's lists (case, spaces, dots, colons and hyphens are folded, and a leading "do not", "don't", "no", "not", "never", "avoid", "without" or "prohibited:" on a prohibited entry is ignored). The limits come from the form answers stored with the agreement, not from its text. It reads the delegation templates (general authorization, power of attorney, limited service, fleet) and the commerce templates (API access, compute SLA, task execution). If the agreement was amended, the newest approved version is checked. Free: no credits are burned. Amounts are compared in USD (USDC counts as USD) or in the template's own currency; a payment in another currency is not compared and the verdict is "incomplete". It does NOT read the agreement's human-readable text. Anything written in words (the scope, conditions, geographic limits, who may be paid, how a limit is measured) is for you to read yourself: always read the agreement's scope and conditions before acting on any answer. The response's "not_checked" lists, by path and never the text, parts to start with (each has a kind and a short reason; at most thirty are listed, "not_checked_count" has the total). It is a best-effort hint, not a complete list: an empty or short list does not mean there is nothing to read. Read the agreement itself through the contract read. Verdicts: - "within_limits": the template is one the check reads, the form answers are stored and valid, every limit they set was evaluated and passed, every figure written in digits or in common number words in the agreement's machine-readable text is accounted for, and at least one spending limit or price was evaluated. It says nothing about terms written in words. - "out_of_scope": a limit definitely fails (status, validity window, a cap, a payment that must equal what is left of a task price, a category or action that is not on a list held in the form answers, or that is prohibited). A permitted-action or category list found only in the agreement's text is never trusted to decide this: a miss there is "incomplete". - "needs_approval": an approval or escalation threshold is exceeded. "also_incomplete": true then means some limit could not be evaluated either; the reasons still carry it. - "incomplete": something could not be checked or placed: an input you did not send (category, action, currency, period_spent), a form answer the check cannot use, a figure or statement in the agreement's text that the form answers do not explain or contradict, wording beside a limit that names another period than the one period_spent covers, a date the check cannot place as the agreement's end, a miss on a permitted-action or category list found only in the agreement's text, a payment that is not a whole number of calls at the price per call, permitted counterparties (the request carries none), a payment model the check cannot match, an agreement without stored form answers or made from another template. Ambr does not hold funds or track spend: period_spent is what was already spent in the period the limit covers (this month for a monthly limit, fee or fleet budget, for a fleet the whole fleet's; the whole agreement so far for a total budget or task price). One payment above a limit fails without it. Access: a public contract is open to anyone; otherwise use the creator's API key or pass a share_token. Args: - contract_id (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID - amount (number, required): payment amount, zero or more - currency (string, optional): e.g. "USD" - category (string, optional): your own category label, matched exactly against the agreement's list - action (string, optional): the action the agent is taking, matched exactly against the agreement's lists - period_spent (number, optional): already spent in the period the limit covers (this month, or the whole agreement for a total budget) - share_token (string, optional): share token for a private contract Returns: verdict ("within_limits" | "out_of_scope" | "incomplete" | "needs_approval"), the per-rule checks, plain-language reasons, "not_checked" and "not_checked_count", "also_incomplete" when it applies, and the contract that was checked (contract_id, effective_contract_id, sha256_hash, reader_url).
Connections
streamable-http
https://getamber.dev/api/mcp