Embrace · Rate Limits

Embrace Rate Limits

Name: Embrace Rate Limits
Creator: Embrace
Keywords: Company, Observability, Monitoring, Mobile, Real User Monitoring, OpenTelemetry, Metrics, Crash Reporting, Application Performance Monitoring, Developer Tools, Model Context Protocol

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.

14 Limits

CompanyObservabilityMonitoringMobileReal User MonitoringOpenTelemetryMetricsCrash ReportingApplication Performance MonitoringDeveloper ToolsModel Context Protocol

Limits

session_properties per-session

100

info_logs per-session

100

warning_logs per-session

200

error_logs per-session

500

log_message_length per-log

4000

log_attributes per-log

100

breadcrumbs per-session

100

custom_spans per-session

500

automatic_spans per-session

5000

span_attributes per-span

100

span_events per-span

network_requests per-session-per-domain

1000

webview_events per-session

100

exceptions per-session

500