Agentic Fabriq
Mixpanel
DATA · DATA & ANALYTICS
Funnels, retention, segmentation, and cohorts over their own project data.
Connecting Mixpanel in practice
Mixpanel’s Query API allows a maximum of 5 concurrent queries and 60 queries per hour, which is the real ceiling on any agent that reads reports, while ingestion is comparatively unlimited at 2GB of uncompressed JSON a minute. It also rejects any event timestamped more than 1 hour in the future and deduplicates on the tuple of event, time, distinct_id and $insert_id.
Rate limits
- Ingestion: 2GB of uncompressed JSON/minute or ~30k events per second, measured on a rolling 1 minute basis; up to 2000 events and 10MB per /import request.
- Query API: a maximum of 5 concurrent queries and 60 queries per hour.
- Raw data export API: a maximum of 100 concurrent queries, 60 queries per hour, and 3 queries per second.
- Lexicon Schemas API: a maximum of 5 requests per minute, under 4000 events and properties updated in each minute, and less than 3000 total truncations/deletions per request.
- All limits are enforced at the project level, and overage returns 429.
Worth knowing
- Events with a time value before 1971-01-01 or more than 1 hour in the future are rejected, and future-dated events are overwritten with ingestion server time, so clock skew silently rewrites history.
- $insert_id must be at most 36 bytes of alphanumerics or hyphens and cannot be a string like null, undefined or 0, which are exactly the values a buggy client sends.
- Import errors are silent unless strict=1 is passed, which is why a pipeline can look healthy while dropping events.
- Each event can have up to 255 properties, names and values are truncated at 255 characters, and the soft limits of 5000 distinct event properties and 5000 distinct event names per project mean extra properties are ingested but never indexed or autocompleted.
Checked against Mixpanel rate limits (2026-09-29), Import events endpoint (2026-09-29), Events and properties limits (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Mixpanel behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.