Set
Authorization: Bearer <fhddos-token> on every request. Your Fhddos token starts with oh-.How it works
Fhddos sits between your application and the upstream AI providers. Because the API surface mirrors OpenAI’s REST specification, you only need to change two things in your existing code:base_url→https://aiapi.fhddos.comapi_key→ your Fhddos token (starts withoh-)
If your account connects to both official and economy provider groups, restrict your OpenAI compatibility promise to the official group. See the video-generation page for details on group isolation.
Set up your environment
Export these two variables once and every subsequentcurl or SDK example on this site will work without modification.
Quick test
Verify your token is valid and see which models you have access to:list object whose data array contains model objects. If you see an 401 error, double-check that your token begins with oh- and is correctly set in the Authorization header.
Key capabilities
| Feature | Description |
|---|---|
| Official compatibility | Under official groups and channels, the API stays aligned with OpenAI’s REST spec. Reuse existing SDKs and code with zero logic changes. |
| Unified authentication | One Fhddos token accesses multiple providers. Apply fine-grained key permissions and usage monitoring from the Fhddos console. |
| Multi-cloud routing | Switch backend providers or enable redundancy strategies from the console without touching your application code. |
Explore the API
Chat Completions
Classic conversational interface with streaming, tool calling, and JSON mode.
Responses
Unified multimodal interface supporting text, images, and structured output in one request.
Audio
Text-to-speech, audio transcription, and translation with Whisper models.
Images
Generate and edit images with gpt-image-2, including async task workflows.
Video
Create Sora videos, poll for completion, and download MP4 results.
Models
List all models your token is authorized to use.
