Core Concepts

Before you integrate AnyInt, it helps to think about the platform in terms of a few core ideas.

Concept map

Concept	What it means	Where to verify
API family	A route family with its own request body and auth conventions	API Reference
Model ID	The exact string sent in the `model` field	Models API
API key	Credential used to authenticate gateway requests	API Keys
Project or team key	A key scoped for a team, environment, or workload	Team Keys
Task ID	Identifier returned by async media or music workflows	Media & Music
Callback	A customer-owned URL that receives async task events when supported	Webhooks and Notifications
Fallback	A secondary model or route path used under an explicit policy	Model Fallbacks

1. One gateway, multiple model families

AnyInt is one platform, but it exposes multiple route families:

OpenAI-compatible
Anthropic-compatible
Gemini-compatible
media generation
AI Music

That means "one platform" does not mean "one request shape". It means one operational layer across multiple AI surfaces.

Family	Typical use
OpenAI-compatible	Fast first integration for chat, assistants, and many SDKs
Anthropic-compatible	Claude-style messages and content blocks
Gemini-compatible	Gemini-native `contents[].parts[]`, streaming, and function flows
Media generation	Image and video generation routes
AI Music	Songs, covers, lyrics, stems, and music video workflows

2. Easier access is part of the product

AnyInt is not only a relay. One of its core purposes is reducing the effort required to use advanced AI models.

That includes:

fewer provider-specific integrations
fewer billing surfaces
one place to manage keys and access
one docs set for multiple workflows

3. Model choice is a product problem

Many users know what task they want to solve, but they do not know which model is the best fit. This is why model selection should not be treated as a purely manual decision.

In many real cases:

multiple models can achieve the same acceptable result
the highest-priced model is not always necessary
the biggest challenge is matching task requirements to the right model and price point

4. Smart Routing (Coming Soon) is about better defaults

Smart Routing (Coming Soon) should be understood as a model-selection layer, not just a transport feature.

Its value is:

choosing models more appropriately
avoiding unnecessary premium-model usage
improving the balance between quality, latency, and cost

5. Model IDs are the source of truth

Do not guess model IDs. Fetch them from GET /openai/v1/models or use the list available to your account. Availability can differ by account, billing mode, plan, or purchase configuration.

6. API keys connect access and billing

API keys are the main authentication mechanism for platform access. Depending on the route family you call, the header format may differ:

Authorization: Bearer <key>
x-api-key: <key>

Keys also connect to billing mode, because requests may consume prepaid balance, subscription entitlement, or team-managed access policy.

7. Async tasks are normal for media workflows

Not every route returns a final artifact immediately. Media and AI Music workflows commonly follow this pattern:

create a task
receive a task ID
poll a query endpoint or wait for a webhook
download the generated artifact

Common mistakes

Mistake	Correct model
Assuming one gateway means one JSON schema	Match the body to the API family
Copying a model name from marketing material	Use the exact `data[].id` returned by the Models API
Treating task creation as a finished asset	Poll or handle callbacks until success
Reusing one key everywhere	Separate keys by environment, project, or team
Treating fallback as automatic	Define when fallback is allowed and log it

The mental model to keep

Think of AnyInt as:

an easier way to access advanced AI models
a platform for better model selection
a gateway for multiple API families
a control surface for billing, keys, and policy
a workflow layer for async media and music generation

On this page