Trubrics Rate Limits
The Trubrics ingestion API constrains throughput primarily through a documented batch limit of up to 100 events per publish request on both the publish_events and publish_llm_events endpoints. The SDKs queue events and flush on a configurable interval (default 10 seconds) or queue size (default 20 events) to batch writes efficiently. Account-level requests-per-minute or per-day quotas are not published and are not reconciled in this artifact.
Trubrics Rate Limits is the machine-readable rate-limit profile for Trubrics on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring events, seconds, and requests.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include AI, LLM, Product Analytics, Event Tracking, and Rate Limiting.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/trubrics-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.