Provider catalogues mix three kinds of entry on one page: models you can call now, models you can ask for, and models the provider only tested. They look alike in a table. They are very different when you write code against them. This post shows how to tell them apart, using BroadNet’s catalogue as the worked example. BroadRouter is BroadNet’s own site, so we checked every BroadNet page cited here on 15 November 2026 and quote it rather than paraphrase where it matters.
What are the three kinds of catalogue entry?
| Status | What it means | What you need | How you call it |
|---|---|---|---|
| Live | On the public rate card with a published price | An account and an eligible key | The public model ID on the public base URL |
| On request | The provider can deploy it, but not self-serve | An enquiry and an agreement | Usually a private model ID or endpoint |
| Research | Tested, benchmarked, quantised or ruled out | Nothing; it is not for sale | You can’t |
The trap is the third row. A provider that publishes its research honestly will list far more models than it sells. That is useful information about how it chooses models. It is not an availability claim.
How does BroadNet’s catalogue show it?
BroadNet’s model catalogue has all three on one page, in this order:
- “Live on the Inference API”. The box says: “These models are on the rate card today.”
- “Available on request”. Three entries: a BroadNet fine-tune of Cohere Transcribe Arabic, Qwen3-VL 30B-A3B Instruct and Qwen3-VL 8B Instruct. Their model pages say “private id issued per customer”.
- “The catalogue”. Every model BroadNet says it has run in its lab (about 270, measured in September 2026), tagged PROD (carried live traffic), SERVED, BENCH, QUANT, FT or RULED OUT. It is grouped into language models, speech to text, text to speech, OCR, embeddings, image and video generation, and more.
- “Remote and API models benchmarked”. In BroadNet’s words: “About 90 models we never ran on our hardware but pushed through our safety, routing and Arabic harnesses.” It names models from Anthropic, OpenAI, Google, Meta and others.
Only the first group is callable with a self-serve key. The third and fourth groups include text-to-speech, image-generation and embedding models, none of which BroadNet’s public API offers. Seeing FLUX or a Claude model in the table tells you BroadNet measured it, not that you can send it a request. The reasons BroadNet gives for the rejected ones are summarised in models BroadNet ruled out, and the hardware side in BroadNet’s GPU hardware and serving.
Which source is the rate card?
The machine-readable one. BroadNet publishes pricing.json, which its API reference describes as “the same file our pricing and plans pages are built from”. For each model it gives:
id: the exact string to send asmodel;status:liveoron_request;paid_only: true when the model opens only after a qualifying top-up;- prices,
context_length,modalitiesfor chat models, andlanguagesfor transcription.
On 15 November 2026 the feed listed six live models: DeepSeek V4.1 Flash, GLM 5.3, Qwen3.8 27B, Gemma 4 VL 26B, BroadNet Transcribe Arabic and BroadNet Transcribe. The API reference’s model table listed the same six IDs.
The catalogue page’s “Live on the Inference API” box, on the same day, showed four of them: it left out GLM 5.3 and Qwen3.8 27B, and still did when we rechecked on 16 November 2026. (Qwen3.8 27B appeared lower down as SERVED in the lab table.) We don’t know which page is behind, and we could not confirm with a paid request. This is normal on any provider’s site, and it is why you should read the feed and the API reference for what to send, then test.
Can you trust GET /v1/models?
Check what it means for each provider. The OpenAI Python SDK documents models.list() as listing “the currently available models”, and many tools call it to fill a model picker. Other OpenAI-compatible APIs implement it differently.
BroadNet’s API reference says: “Use the model IDs in this reference for direct API requests. GET /v1/models supplies public catalogue metadata for external monitors.” When we called it on 15 November 2026, without a key, it returned only broadnet/cohere-transcribe-arabic and broadnet/cohere-transcribe, each with fields such as input_modalities, capacity and an is_ready flag set to false. None of the four live chat models was listed. So a tool that builds its model list only from /v1/models would show no chat models for BroadNet; type the model ID in by hand, as the OpenAI-compatible base URLs post describes for other clients.
How do you check status in code?
This script reads BroadNet’s public feed and /v1/models, both without a key, and prints each model’s status and access. It is safe to run in CI to catch a model being added, moved to on-request or retired.
import json, urllib.request
FEED = "https://inference.broadnet.ai/pricing.json"
MODELS = "https://inference.broadnet.ai/v1/models"
def get(url):
req = urllib.request.Request(url, headers={"User-Agent": "catalogue-check/1.0"})
with urllib.request.urlopen(req, timeout=30) as r:
return json.load(r)
feed = get(FEED)
assert feed["schema_version"] == 1, "unknown feed schema: re-read the docs before trusting it"
print(f"prices updated {feed['updated']}")
for m in feed["models"]:
status = m.get("status", "live") # docs: live or on_request
access = "top-up required" if m.get("paid_only") else "open from sign-up"
inputs = ", ".join(m.get("modalities", [])) or f"audio, {m.get('language_count', len(m.get('languages', [])))} language(s)"
print(f"{status:10} {m['id']:36} {m['kind']:5} {inputs:22} {access}")
listed = {m["id"] for m in get(MODELS)["data"]}
callable_ = {m["id"] for m in feed["models"] if m.get("status", "live") == "live"}
print("live in the feed but not in /v1/models:", sorted(callable_ - listed))
print("in /v1/models but not live in the feed:", sorted(listed - callable_))
Run live on 15 November 2026, it printed:
prices updated 2026-11-14
live broadnet/deepseek-v4.1-flash chat text, image top-up required
live broadnet/glm-5.3 chat text top-up required
live broadnet/qwen3.8-27b chat text, image top-up required
live broadnet/gemma-4-26b-a4b chat text, image open from sign-up
live broadnet/cohere-transcribe-arabic stt audio, 1 language(s) open from sign-up
live broadnet/cohere-transcribe stt audio, 14 language(s) open from sign-up
live in the feed but not in /v1/models: ['broadnet/deepseek-v4.1-flash', 'broadnet/gemma-4-26b-a4b', 'broadnet/glm-5.3', 'broadnet/qwen3.8-27b']
in /v1/models but not live in the feed: []
“Open from sign-up” is our script’s label for a row without paid_only, not a field in the feed; on BroadNet that means the $5 starting credit reaches it. The schema_version check follows the docs, which say the version changes only when an existing field changes meaning, and that new fields can appear at any time.
The final check is a request. A cURL quickstart call with the model ID and a short prompt returns 200 if the model is live for your key, and an error with a machine-readable code if not.
What does “on request” look like in practice?
BroadNet’s on-request model pages show what changes. The Qwen3-VL 30B-A3B page, for example, has an “Ask for access” button instead of a price, lists the model ID as “private id issued per customer”, and gives a 16K-token context. The BroadNet fine-tune of Cohere Transcribe Arabic works the same way. BroadNet’s API reference explains the mechanism: private endpoints, its Arabic fine-tunes and other models on request “are reached with a private ID issued with the endpoint.”
Three consequences for your code and your plans:
- No public ID to hard-code. You can’t write the request until the provider issues the ID, so keep the model ID in configuration, not in code.
- Different limits. An on-request deployment can have a different context window, rate limit and region from anything on the public rate card. Ask for them in writing.
- Different terms. BroadNet’s Terms say private endpoints and reserved capacity follow a separate written agreement. Prices, availability and processing location come from that agreement, not from the public pages.
A five-step check before you build on a model
Run this for every model you plan to depend on, at any provider:
- Find it on the rate card or feed, not only in a blog post, a model page or a benchmark table.
- Copy the exact ID from the API reference. Names drift: version suffixes, “Flash” and “Pro” variants, and provider prefixes like
broadnet/all matter. - Check access. Does your key or plan cover it? On BroadNet,
paid_onlymodels need a top-up, and the DeepSeek session plans cover DeepSeek V4.1 Flash only. - Check the capability you need on that model, such as images, tools or structured output, in the docs. A capability on one model says nothing about the next.
- Send one request with a realistic prompt, and keep the response’s request ID. Repeat in CI if the model is critical.
What should you never infer from a catalogue?
- That a benchmarked model is for sale. A row in a research table is a measurement.
- That on request means soon. It means a conversation. BroadNet presents on-request models, private endpoints and regional processing as enquiries through its contact page; see planning a private endpoint.
- That a capability applies to every model. BroadNet’s docs say vision is “offered only where the model row explicitly says images or vision”, and document tool calling for GLM 5.3 and Qwen3.8 27B only. Text, speech or vision maps tasks to the models that take each input.
- That today’s list is permanent. BroadNet’s Terms (§7.4) say it may change, suspend or retire a model or feature and, where it can, give reasonable notice on the catalogue page. Self-serve has no availability commitment; service levels exist only in a separate written agreement.
- That a model name means the same model everywhere. BroadNet’s remote list includes “GLM 5.3 Flash”, which is not the
broadnet/glm-5.3on its rate card. Always copy the exact ID.
The same checks apply to any provider. Our provider checklist has the rest of the questions to ask.
Where BroadNet Inference fits
BroadNet Inference’s live models and prices are on our models and pricing pages, built from the same pricing.json. Models BroadNet offers on request are listed separately under on request. The research catalogue on broadnet.ai is worth reading for how BroadNet chooses models, and for its published reasons for rejecting some, but treat every row in it as evidence, not as an offer.
