API Reference
Authentication
Connect to Infe using your API key with Bearer authentication.
Base URL
All API requests should be made to:
https://api.infe.io/v1
Authentication
Infe uses API keys for authentication. Include your key in the Authorization header:
Header
Authorization: Bearer infe_your_api_key_hereSecurity Best Practices
- • Never commit API keys to version control
- • Use environment variables in production
- • Rotate keys periodically from your dashboard
- • Use separate keys for development and production
API Key Format
Infe API keys follow this format:
infe_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Keys are 32 characters following the infe_ prefix
Request Format
All requests must include:
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer {api_key} | Yes |
| Content-Type | application/json | Yes |
Response Headers
Infe includes helpful headers in every response:
| Header | Description |
|---|---|
| x-request-id | Unique request ID for debugging |
| x-infe-region | Edge region that handled the request |
| openai-processing-ms | Total processing time in milliseconds |
| Infe-Unit-Cost | Credits consumed for this request |
| x-ratelimit-remaining-requests | Remaining requests in rate limit window |
Rate Limiting
Rate limits vary by plan. When you exceed your limit, you'll receive a 429 Too Many Requests response.
| Plan | Requests/min | Tokens/min |
|---|---|---|
| Free | 20 | 10,000 |
| Starter | 100 | 100,000 |
| Pro | 500 | 500,000 |