Faros AI · Rate Limits

Faros Rate Limits

Faros AI authenticates API and GraphQL requests with a per-account API key passed in the Authorization header. The platform does not publish committed public rate-limit values for the events/ingestion REST API or the Hasura GraphQL query endpoint; throttling, quotas, and any per-tenant limits are governed by the customer's plan and are not reconciled in this artifact.

Faros Rate Limits is the machine-readable rate-limit profile for Faros AI on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Engineering Operations, Software Engineering Intelligence, SEI, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Engineering OperationsSoftware Engineering IntelligenceSEIRate LimitingQuotasThrottling

Limits

REST Events / Ingestion API account
requests
see provider documentation
Event and model-write throughput against prod.api.faros.ai; not publicly published.
GraphQL Query API account
requests
see provider documentation
Hasura GraphQL endpoint POST /graphs/{graph}/graphql; limits not publicly published.
Webhooks webhook
requests
see provider documentation
Inbound webhook delivery to /webhooks/{webhook_id}/events; not publicly published.

Policies

API Key Authentication
All requests require a Faros API key in the Authorization header; revoke and rotate keys in the Faros application.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources