Ambr · Rate Limits

Getamber Dev Rate Limits

Ambr documents rate limiting in one paragraph of its developers page ("Errors & rate limits"): "Several write endpoints are rate-limited, per IP or per API key (revocation allows 5 requests per minute per IP). Back off and retry after retry_after_ms on 429." The only numeric limit published is the revoke endpoint's; the other write limits are stated to exist but not quantified. The 429 body carries the error code rate_limited and a retry_after_ms field — the retry signal is IN THE BODY, not a Retry-After or RateLimit-* header. The 0.2.0 changelog entry (2026-04-10) lists "rate limiter" under security hardening. Probed 2026-09-19: twelve consecutive anonymous GETs to /api/v1/pricing all returned 200 with no RateLimit-*, X-RateLimit-* or Retry-After headers, so read endpoints expose no per-request quota signal. limit_count reflects the one quantified limit; the unquantified write limits are recorded below with limit null rather than invented.

Getamber Dev Rate Limits is the machine-readable rate-limit profile for Ambr on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_minute and requests.

Limit state is signalled in the rateLimit, rateLimitRemaining, rateLimitReset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

The profile also includes response codes documented for throttled, errorCode, and bodyField.

Tagged areas include Company, AI Agents, Agentic Commerce, Contracts, and Legal.

2 Limits Exhausted: HTTP 429 rateLimitrateLimitRemainingrateLimitResetretryAfter
Transcribed from the provider's documentation on 2026-09-19 — getamber.dev/developers.
View Source
CompanyAI AgentsAgentic CommerceContractsLegalRicardian ContractsDelegationBlockchainBase L2MCPA2Ax402Agent-Native

Limits

Revoke contract ip
POST /api/v1/contracts/{id}/revoke
requests_per_minute · minute
5
Other write endpoints per IP or per API key (docs do not say which applies to which)
POST /api/v1/contracts, /handshake, /sign, /keys and other writes
requests
Documented as rate-limited ("Several write endpoints are rate-limited, per IP or per API key") but no number is published.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/getamber-dev-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.