What ModelBeat is

ModelBeat is a routing gateway for the multi-model era. You hold one API key and one prepaid balance; for each request ModelBeat decides which model serves the work, executes it against a pool of providers, and returns the response with full per-request token and cost accounting.

It speaks the OpenAI API, so most integrations are a two-line change.

The two-line change

from openai import OpenAI

client = OpenAI(
    api_key="mb_live_EXAMPLE_NOT_A_REAL_KEY_00000000000000000000",
    base_url="https://api.modelbeat.ai/v1",
)

r = client.chat.completions.create(
    model="auto",
    messages=[{"role": "user", "content": "hello"}],
)

What you get that a provider does not give you

Every successful response carries two ModelBeat-specific things:

• extra_fields.routing_info tells you which model actually served the request, whether it was a fallback, and what was originally targeted. See Routing transparency.
• usage.cost is what the call cost, broken down by component. See Costs.

Read this before you build

ModelBeat is in private beta and the published API surface is deliberately narrow: two metered endpoints. Limits says exactly what is and is not supported. Read it first. The constraints will otherwise surprise you late, when they cost an afternoon.

Next

• Quickstart. A working call in a couple of minutes.
• Authentication. Keys, headers, rotation.
• API reference. The full contract, with a request playground.