Get in touch
Questions, problems, volume pricing.
What to send
- Getting a key
- Sign in to the console and create keys yourself. Your first sign-in creates your account. Balance is prepaid from $10, with no subscription. Write to us if something in that flow stops you.
- A request that failed or looks wrong
- Send the request id. Every API response, errors included, carries it in the x-uplink-request-id header, and the console's Usage page lists every request with its id. Add the model, the time in UTC, the status code and which SDK or tool you use.
- A charge you want explained
- Give the request id or the month. Each month has a signed statement and a CSV of every request on the console's billing page. You can check a statement is genuine before you send it.
- Volume pricing
- We can set a rate for one account. Tell us the models and the tokens you expect a month. The bill rewriter shows what your last bill would cost at today's prices.
- A model or a format
- Every model, price and supported SDK format is on the models page and in GET /v1/catalog. Ask us about one that is missing.
- A security problem
- Email hello@uplinkswitch.com with the steps to reproduce it. Please do not post it in public first.
Check these first
- Status: every route probed hourly, with 30 days of history.
- Guides: settings for the OpenAI, Anthropic and Gemini SDKs, Claude Code, Cursor, Cline and other tools.
- Proof: a daily check that each model is the one named.
- Changelog: what changed and when.
- About UplinkSwitch: who runs it and how prices are set.
The form sends one email to hello@uplinkswitch.com after an invisible Cloudflare Turnstile check. The message itself is not stored. A subject can be up to 150 characters and a message from 10 to 5,000. Replies go to the address you give.