The test passes but the run fails.

The test is one small call; a run is thousands. Rate limits and per-minute quotas are the usual difference. Raise the limit for the duration, or tell us and we will pace it.

Does the test cost me tokens?

A negligible number. It is deliberately the smallest billable unit your provider supports, and for some shapes it is a metadata read that costs nothing at all.

Can I test again later?

Yes, from your models page, as often as you like. It is free and it does not touch your evaluation allowance.

SUBMITTING A MODEL

Connecting your endpoint

What the connection test actually does, and how to read each failure it reports.

Test Connection makes one small, cheap call to your endpoint before anything is spent. It exists so a wrong key costs you a click rather than an evaluation.

What it checks

That the base URL resolves and answers over HTTPS.
That the API key authenticates.
That the model identifier exists at that endpoint.
That the retention parameters we send are accepted rather than rejected.

Reading a failure

What it says	What it usually means
The endpoint returned 401 or 403	The key is wrong, expired, or scoped to a different project.
The endpoint returned 404	The base URL or the model identifier is wrong. Check the identifier against your provider's own model list.
Your endpoint rejected the data retention parameters	The provider does not support zero data retention on this route, or the account is not enabled for it.
The endpoint did not answer in time	A cold start, a firewall, or a region that is slow from Europe. Try once more before changing anything.
The URL contains a username and password	Credentials belong in the API key field, not embedded in the URL.

Questions we get asked

Was this page helpful?