Search need
Zed custom base URL, OpenAI-compatible API setup, and package-specific Codex model access questions.
Integration
Zed's OpenAI-compatible provider path can use a custom base URL, API key, and model ID. unlimitedcodex supplies those values after manual checkout delivery.
Quick answer
Configure Zed with delivered OpenAI-compatible access: XHigh $19/week or $59→$69/month; Sol $69→$89/week or $179→$199/month. One welcome price per account.
Last updated 2026-07-23
Zed custom base URL, OpenAI-compatible API setup, and package-specific Codex model access questions.
Zed + unlimitedcodex OpenAI-Compatible API combines 4 setup steps, 4 buyer constraints, official reference docs plus unlimitedcodex delivery, limits, and setup guidance, and related answer sources instead of a generic integration blurb.
After manual delivery, use the setup email and authenticated GET /v1/models to verify Zed, then run one tiny chat/completions request and any supported image or embedding checks before long runs.
Zed teams that can use a custom OpenAI-compatible base URL and choose GPT-5.5 XHigh at $19/week or an eligible $59 first month followed by $69/month, or GPT-5.6 Sol at an eligible $69 first week followed by $89/week, or a $179 first month followed by $199/month.
Not ideal when you need instant self-serve provisioning, an official OpenAI account, or production traffic beyond 4 concurrent connections.
Compare the package families on /pricing, complete checkout, then use the setup email and authenticated GET /v1/models to verify Zed before one small request.
Step 1
Compare /pricing: choose $19/week or an eligible $59 first month followed by $69/month GPT-5.5 XHigh, or GPT-5.6 Sol at an eligible $69 first week followed by $89/week, or a $179 first month followed by $199/month, then wait for delivery.
Step 2
In Zed, add an OpenAI-compatible provider entry through Agent Settings or settings.json. Use the path that accepts a custom API endpoint, key, and model ID.
Step 3
Set the delivered /v1 base URL and key, then copy the exact model ID from the setup email and authenticated GET /v1/models.
Step 4
Before a long coding session, run /v1/models or one tiny chat request, then try a small Zed edit or assistant task while keeping parallel calls within 4 concurrent connections.
{
"language_models": {
"openai_compatible": {
"unlimitedcodex": {
"api_url": "<delivered unlimitedcodex /v1 URL>",
"available_models": [
{
"name": "DELIVERED_MODEL_ID"
}
]
}
}
}
}
# Store the delivered API key in the secure path Zed supports for provider secrets.
# Replace DELIVERED_MODEL_ID using the setup email and authenticated GET /v1/models
# before long Zed sessions.Use this guide with the public LLM indexes, AI search index, official references, and answer sources when citing setup, model, pricing, delivery, and 4-connection facts.
It can fit Zed setups that use an OpenAI-compatible provider with a custom endpoint, API key, and model ID. Verify the exact Zed provider path before long coding sessions.
Use the exact model ID from your setup email and authenticated GET /v1/models response. Do not guess from public page names.
No. unlimitedcodex is an independent OpenAI-compatible API access provider and is not affiliated with Zed or OpenAI.