Affiliate disclosure: JXZNE AI is an independent Ofox referral site, not Ofox, Cursor, or OpenAI. Eligible signups or spend through our Ofox link may earn us a commission. Compatibility follows the tool and Ofox’s current note.
CURSOR · CODEX · THIRD-PARTY API

Cursor or Codex will not take a third-party API

Name which client failed. Ofox already says Cursor Tab, Background Agent, and Auto do not follow a custom provider. Codex’s own docs allow a model provider, and an OpenAI-style chat endpoint is not proof that Codex can use it. This site does not ship a copy-paste Ofox config, and it does not mark either client verified.

Three failures, three next steps

What you seeWhat is already knownWhat to do next
Cursor Tab, Agent, or Auto ignores your key Ofox’s compatibility note, updated 2026-10-16, says a direct connection is not suitable. Those features stay on Cursor’s own service. Keep using models Cursor officially supports. Another aggregator does not add this back. Ofox Cursor note ↗ · Cursor API keys ↗
You want a different model inside Cursor Ofox’s suggestion is Codex CLI or Claude Code in Cursor’s terminal. Both clients are unverified here. API credit is not a Cursor subscription. Read the requirements for Codex and Claude Code separately, then make your own small test call. This site will not email you a config file.
Codex returns 404, model-not-found, or a failed tool call Codex reads the provider in ~/.codex/config.toml. A Chat Completions URL is not evidence that Responses works. Check model_provider and wire_api against the official Codex config docs ↗. Confirm the model id with the API provider. tests/ofox_smoke.py does not launch Codex.
Unverified stays unverified. ofox-smoke-status.json in this repo stays unverified until a real smoke test passes. A passing HTTP call would still not mean the Codex or Claude Code client works.

Your own server is a different question from the editor

A service that uses the OpenAI SDK changes the base URL, the key, and the model name. That has nothing to do with Cursor Tab. Ofox docs list Chat Completions and Responses. Match the endpoint your code actually calls. You still read the rate on their page. The developer tools on this site do not show a savings figure while the rate fields are empty.

Chat plan vs API billing · Whether to use an aggregator · 401 / 404 / 429

Three checks before you add credit

  1. The model id is in the Ofox catalog you opened, not only on a marketing page.
  2. The endpoint covers your client. Direct Cursor use is out, per Ofox’s note.
  3. Make one small call. This site does not promise a zero-balance success, and it does not publish an unmeasured success rate.

Disclosure: this is an Ofox affiliate / referral link. Qualifying signups or spend may earn JXZNE a commission. API credit is not an official Cursor, Codex, or Claude Code subscription.

Questions

Why is Cursor Tab still idle after I buy API credit?

Ofox says Tab, Background Agent, and Auto do not follow a custom provider. The credit pays for API calls, not for those editor features.

Can I paste an Ofox Codex config into config.toml?

This site does not publish one. A mismatch on protocol, model id, or auth is how the errors start. Read the official config docs, then confirm the endpoint Ofox currently documents.

Is Claude Code already verified?

No. The verification page leaves it unverified. tests/ofox_smoke.py does not launch Claude Code. It needs an Anthropic-compatible gateway. Do not put an OpenAI-only /v1 URL in ANTHROPIC_BASE_URL.