Embrace Rate Limits
Embrace documents NO HTTP rate limits and NO rate-limit response headers on any of its programmatic surfaces — not the Metrics API, not the Custom Metrics API, not the MCP server. An agent calling Embrace has no runtime signal telling it when to back off. What Embrace does publish, in detail, is a set of per-session INGESTION CAPS enforced by the SDKs and the backend. Those are recorded below as kind: ingestion-cap so they are never mistaken for request quotas.
Embrace Rate Limits is the machine-readable rate-limit profile for Embrace on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 14 rate-limit definitions.
Tagged areas include Company, Observability, Monitoring, Mobile, and Real User Monitoring.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.