Authentication & API hosts
Vision APIs are currently delivered through RapidAPI. Each request uses your RapidAPI key and the host for the selected API.
Required headers
| Header | Value |
|---|---|
X-RapidAPI-Key | Your authorized RapidAPI application key. |
X-RapidAPI-Host | The host shown on the selected API’s endpoint page. |
Choose the matching host and subscription
The face comparison and face attributes endpoints share one listing. AI detection, passport OCR, and moderation each have a separate listing. Choose the host and subscription for the API you call; a plan for one listing does not automatically grant access to the others.
Keep credentials on your server
Route requests through your application’s backend. Do not embed a RapidAPI key in a public JavaScript bundle, a downloadable mobile application, a URL, or source control. Configure it through your hosting platform’s secret management.
Multipart requests
Use multipart/form-data for image uploads. Let your HTTP client set the Content-Type boundary. Passport scan uses the field front; face comparison uses source and target; other single-image endpoints use image.
Plans and limits
Current pricing, quotas, billing terms, and rate limits are published on each RapidAPI listing. They may differ between APIs and plans. These docs do not imply a shared quota or a direct Tigrate billing plan.