Skip to main content
Before making your first inference call, you can query GET /v1/models to discover exactly which models your Fhddos token grants access to. The response follows the standard OpenAI model list format, so any tooling or SDK that already works with the OpenAI /v1/models endpoint works here without modification.

​
Endpoint

GET https://aiapi.fhddos.com/v1/models
The list is scoped to your token — different tokens may return different sets of models depending on which model groups and providers your account is configured to access.

​
Request

curl "https://aiapi.fhddos.com/v1/models" \
  -H "Authorization: Bearer $TOKEN"

​
Response

The response is a standard OpenAI-compatible list object. Each entry in data represents one model your token can call. 
{
  "object": "list",
  "data": [
    {
      "id": "gpt-4o",
      "object": "model",
      "created": 1706745938,
      "owned_by": "openai"
    },
    {
      "id": "gemini-2.5-flash",
      "object": "model",
      "created": 1706745938,
      "owned_by": "google"
    },
    {
      "id": "claude-sonnet-4-6",
      "object": "model",
      "created": 1706745938,
      "owned_by": "anthropic"
    }
  ]
}

​
Response Fields

FieldDescription
objectAlways "list"
dataArray of model objects available to your token
data[].idThe model ID to use in the model parameter of inference requests
data[].objectAlways "model"
data[].createdUnix timestamp of when the model entry was registered
data[].owned_byProvider — e.g. openai, google, anthropic

​
What the Model List Tells You

Use the model list to make your integration more robust:

Dynamic Feature Gating

Check whether a specific model ID is present before showing a feature in your UI. If the model isn’t listed, the feature isn’t available for that user’s token.

Avoid Hardcoding

Pull the model list at startup and cache it locally. This lets you pick up newly added models without redeploying your application.

Monitoring and Rollouts

Combine the model list with Fhddos’s quota policies to do model-level grey rollouts — gradually expose new models to a subset of tokens.

SDK Initialisation

Many third-party frameworks (LangChain, LlamaIndex, etc.) support pre-fetching the model list to populate dropdowns or validate model names before sending requests.

​
Model Coverage

Fhddos aggregates models from multiple providers under a single API surface. Depending on your account configuration, your model list may include:
ProviderExample model IDs
OpenAIgpt-4o, gpt-4o-mini, o3, gpt-image-2
Googlegemini-2.5-pro, gemini-2.5-flash
Anthropicclaude-opus-4, claude-sonnet-4-6, claude-haiku-4
ByteDancedoubao-pro-256k, doubao-lite-32k
OthersVaries by account
The model IDs you see in the list are the exact strings you should pass as the model parameter in your chat, completion, image, audio, or video requests. Using an ID not present in your list will return an authentication or not-found error.

​
Authentication

Authorization: Bearer YOUR_FHDDOS_TOKEN
You can find your token in the API Keys section of the Fhddos console. Tokens are scoped at creation time — contact your administrator if you need access to additional models.