Where your requests go

Who sees a request

Exactly one provider per attempt, plus us. Nothing is broadcast and nothing is mirrored. Which providers exist, what their API base URLs are, and whether this deployment can currently reach each one is public:

curl https://api.multigrid.ai/v1/providers

For one model specifically, the exact order we will try, with the price on each route:

curl https://api.multigrid.ai/v1/models/anthropic/claude-sonnet-5/endpoints

If a request needed more than one attempt, every provider that was tried is on the request row and comes back from GET /generation. So “who handled this specific request” is a question with an answer, not an inference.

Restricting it

provider.ignore removes providers from a request entirely, and provider.allow_fallbacks: false pins it to the first usable route so a failover cannot move it somewhere you did not intend.

{
  "model": "meta/llama-3.3-70b-instruct",
  "provider": { "order": ["together"], "ignore": ["groq", "deepinfra"] }
}

Adding your own provider key is the strongest version of this: the request goes to a company you already have a contract with, under terms you negotiated. See bring your own key.

Region pinning is not built

What we keep

Prompts and completions are never written to our database — not redacted, not briefly. What is stored is token counts, timings, cost, which provider answered and your own metadata labels. There is therefore nothing of your content here to retain, disclose or train on, which is a stronger statement than a retention period would be.

Each provider’s own retention is theirs, governed by the agreement between you and them if you use your own key, and by ours if you use our credit. That is the part this page cannot promise on their behalf.