FAQ
Common errors
Section titled “Common errors”401 Unauthorized
Section titled “401 Unauthorized”- The API key is invalid, expired, or revoked.
- The base URL is incorrect — it must be
https://api.apex1.us(orhttps://api.apex1.us/v1for OpenAI-SDK-style clients). - The auth file (
auth.json/settings.json) is malformed JSON.
Unable to connect
Section titled “Unable to connect”- Confirm your network can reach
https://api.apex1.us. - Check for corporate proxies or firewalls blocking outbound HTTPS.
Model not found
Section titled “Model not found”- Verify the model name against the Supported Models list on the Overview.
- Confirm the model is included in your current plan.
Frequently asked questions
Section titled “Frequently asked questions”Is my data used for training?
Section titled “Is my data used for training?”No. Customer prompts and responses are never used for model training. Want to verify for yourself that no middle party — including us — can even read them? See Privacy Proof.
Do I need separate keys for different tools?
Section titled “Do I need separate keys for different tools?”No. A single ApexOne API key works across Claude Code, OpenCode, Cursor, Cline, and direct API calls. You can create multiple keys in the Dashboard to separate usage by project.
How do I monitor usage and costs?
Section titled “How do I monitor usage and costs?”The ApexOne Dashboard shows all requests, token usage, costs, and cache statistics in real time — with a verifiable inference receipt for every call.
What happens when an upstream provider goes down?
Section titled “What happens when an upstream provider goes down?”ApexOne’s automatic failover reroutes traffic in the background, so your application keeps receiving responses with no code changes. Every failover is recorded in your receipts.
How do I get enterprise access?
Section titled “How do I get enterprise access?”Contact support@apex1.us for enterprise plans, custom SLAs, and volume pricing.
Sharing your subscription
Section titled “Sharing your subscription”Can the person whose subscription served my request read my prompt?
Section titled “Can the person whose subscription served my request read my prompt?”No — not on the shared-subscription route. Providers contribute quota, not servers: the request leaves our TEE and goes straight to the upstream vendor, so it never touches a provider’s device. They only see that their quota was consumed.
There is one route where prompts do reach third-party infrastructure — the provider-supplied API relay — and it is listed explicitly in how your requests are served. Site operators can disable that route entirely.
How much can I earn by sharing my subscription?
Section titled “How much can I earn by sharing my subscription?”We commit to the revenue share — 80% of what the platform charges the user — and to paying it out on-chain with no withdrawal fee. We don’t commit to an amount: that depends on real demand, and the platform is early with demand still building. See Share Your Subscription for the formula.
Why can’t I withdraw my earnings yet?
Section titled “Why can’t I withdraw my earnings yet?”Earnings sit in a 72-hour hold before they become withdrawable — it covers the window in which a consumer’s card payment can still be disputed. See Earnings & Withdrawals.
My account is connected but isn’t earning anything.
Section titled “My account is connected but isn’t earning anything.”Check its state first. An account in the review period is not serving traffic yet — it joins the pool only after passing consecutive probes and clearing the minimum observation window. An account that is serving but earning nothing simply has no demand routed to it.