Developer Preview

The Chameleon Eye API is in developer preview. Rate limiting is planned — it is not actively enforced in the current developer preview. Production limits will be communicated before commercial launch.

API Docs

API Rate Limits

Planned rate limit tiers, error handling, and retry guidance for Chameleon Eye API. Rate limiting is not yet enforced in developer preview.

Planned Rate Limit Overview

Rate limiting is planned for the production API. Limits are not actively enforced in developer preview.

In production, API usage will be plan-limited and rate-limited. Limits will depend on customer plan and contract. Rate limiting is not yet enforced in the current developer preview. Contact the team for early access discussions.

Rate Limit Response Format

When rate limited, the API will return HTTP 429 with the following response body.

{
  "error": "rate_limited",
  "message": "Request rate limit exceeded.",
  "retry_after": 60
}

The retry_after value is in seconds. Wait this duration before retrying.

Best Practices

Follow these recommendations to handle rate limits correctly in your integration.

+Implement exponential backoff on 429 responses.

+Cache intelligence outputs where possible to reduce repeated calls.

+Use webhooks for asynchronous workflows instead of polling.

+Monitor usage via GET /v1/me/usage.

Error Reference

HTTP status codes returned by Chameleon Eye API.

Code	Status	Meaning
401	Unauthorized	Missing or invalid API key
403	Forbidden	Insufficient permissions
409	Conflict	consent_required — user approval needed
429	Too Many Requests	Rate limit exceeded
500	Internal Server Error	Server error, retry later

Back to API Docs Authentication