Models
The Model Hub is the user-facing catalog for model IDs, capabilities, context windows, request examples, provider references, and plan availability. Accly routes requests to third-party provider models; it does not own those models or define their complete behavior.
Find a model in the Model Hub
Use the catalog to find a model and the request format it supports:
- Open the Model Hub — in the app it’s in the sidebar, on the site it’s in the top navigation.
- Filter by modality (Text, Image, Audio), capability, provider, or plan — or search by name.
- Open a model to review its configured context window, capabilities, plan tier, supported API formats, and provider documentation links.
- Copy the model ID from the model page (click the ID to copy it).
- Use that ID only with an endpoint and protocol listed for the model. API-only audio and embedding models are not available in hosted chat.
Model IDs
Use the Accly model ID in the model field of Gateway API requests:
{
"model": "claude-opus-4-7",
"messages": [
{
"role": "user",
"content": "Summarize this release note."
}
]
}Model IDs are shown on each model’s Model Hub page and in the app’s model picker. Availability and capabilities can change with your plan, so read the ID from the Model Hub rather than hard-coding one that may not be available to your account.
Where models appear
Models can appear in these account-aware surfaces:
- Model Hub (
accly.net/models) — the catalog with details and request examples. - Model picker in the chat composer — for using a model in a conversation.
GET /v1/models— the programmatic list for your integrations.
curl https://api.accly.net/v1/models \
-H "Authorization: Bearer $ACCLY_API_KEY"The response uses an OpenAI-style list envelope and includes Accly-safe catalog fields such as model ID, display name, provider family, tier, status, context window, maximum output, and public pricing metadata.
{
"object": "list",
"data": [
{
"id": "claude-haiku-4-5-20251001",
"object": "model",
"created": 0,
"owned_by": "anthropic",
"display_name": "Claude Haiku 4.5",
"provider_family": "anthropic",
"tier": "basic",
"status": "active",
"context_window": 200000,
"max_output": 8192,
"pricing": {
"input": 1,
"output": 5
}
}
]
}Use provider and tier query parameters to narrow the list:
curl "https://api.accly.net/v1/models?provider=anthropic&tier=basic" \
-H "Authorization: Bearer $ACCLY_API_KEY"GET /v1/models and GET /v1/models/{model} require an Accly API key.
Model tiers
Starter, Pro, and Max include the Basic, Advanced, Thinking, and Beta tiers. Free’s Basic tier applies only to hosted app usage; it does not include Gateway API keys. See Plans for the current comparison and quotas. A model’s status, protocol support, and API-key scope still determine whether a request can use it.
API formats
Depending on the model, Accly can expose one or more of these API formats:
- OpenAI-compatible chat completions
- OpenAI-compatible responses
- Anthropic-style messages
- Google/Gemini-style generate content
- OpenAI-compatible embeddings or reranking
- Provider-native audio and speech routes
Use the endpoint shown for that model. The same Accly key authenticates supported route families, but the gateway does not translate a request between incompatible protocols. See Gateway API, Audio & Speech, and Embeddings & Reranking for request examples.
Capabilities
The model catalog can label capabilities such as:
- Streaming
- Vision
- Tools
- Thinking or reasoning-style behavior
- Web search
- Code execution
- Computer use
- PDF, image, video, and audio input or output support
- Context window and maximum output metadata
Not every active model supports every capability. Check the Model Hub or authenticated account catalog before relying on vision, tools, long context, reasoning, audio, embedding dimensions, or other model-specific features.
Do I need provider API keys?
No. Normal Gateway API calls use an Accly API key, not a provider key.
Accly handles provider credentials behind the gateway for supported models. Do not send an OpenAI, Anthropic, Google, or other provider key to Accly endpoints.
Create and manage Accly API keys in Settings → API Keys. The Model Hub provides setup examples for supported protocols and links to provider documentation. Provider documentation is the authority for model-specific prompts, parameter semantics, voice behavior, and upstream changes; Accly documents only the route and validation contract it currently exposes. A provider SDK works with Accly only if it can target the Accly URL and its request protocol matches that route. Keep the key server-side; see Authentication.