glossary · Running it

Provider connection

definition

A provider connection is a named link to one AI model provider that holds the provider key and checks which of its models really answer, so runs only pick models that key can call.

in one line: The key, and proof of which models really answer.

in context

Where does a provider connection fit?

Keys live in the connection. Executors hold no keys. They link connections.

Foundlisted, not called yet
Readya real call worked
Failedwith the reason
Each model on a connection carries a status.
two ways to say it

What is a provider connection, in plain words?

Same idea at two depths: the plain version, then what the engine actually does.

A model in a provider's list is not a model your key can call. A connection checks.

Runs pick only models that answered.

for engineers

provider_connections_manage: create (provider and secret reference), check, link to executors.

Model rows are found, ready or failed; only the check job writes ready.

the longer answer

Why does a provider connection matter?

A model appearing in a provider's list does not mean your key can call it. Plans, regions, credits and rate limits all decide that. Teams usually find out when a run fails halfway with an invalid key or a model not found error.

Keeping the key in a connection object, separate from the agents and runners that use it, solves two problems. The key lives in one place, as a secret, instead of in every runner's configuration. And the connection can check its models ahead of time with one real call each, so the choice of model is made from the ones that work.

in convops

How does a provider connection work in ConvOps?

In ConvOps, a provider connection names a provider, holds its key as a secret reference, and lists the models it offers, each marked found, ready (a real call worked) or failed with the reason. Executors hold no keys; they link connections. When a run picks a model for each agent through its pin, its tier or the executor's own model, a model counts only when it is ready on one of the executor's connections. ConvOps does not sell or host models: the keys and subscriptions are yours.

questions

What do people ask about a provider connection?

Where are model keys kept in ConvOps?

In provider connections, as secret references. Executors hold no keys; they link connections. ConvOps does not sell or host models.

What does ready mean on a connection model?

One real call to that model with the connection's key worked. A model that is only found has not been called yet, and a failed one carries the reason, such as an invalid key.