Delivered API setup
Admin delivery provides the API key, base URL, setup files, activation date, start date, and end date after payment is complete.
Product / API Keys
Use the API key and base URL delivered after payment.
After manual setup delivery, store the OpenAI-compatible API key, base URL, setup files, and access dates, then create, rotate, and revoke scoped workspace keys without interrupting unrelated access.
Control plane
API Keys
Setup path10 min to 5 hours
Storage modelHashed keys
Package limit4 concurrent
Scoped access
Limit credentials by environment, endpoint, or workspace need after the initial delivered setup is available.
Rotation planning
Track key age, ownership, and usage patterns so credential rotation becomes routine instead of reactive.
Revocation logs
See when keys were created, used, rotated, or revoked for clearer security reviews and audits.
Workflow
From setup to launch prep.
Each module is designed to give developers fast integration paths while giving operators the controls they need before traffic scales.
1
Receive setup delivery
After login, package selection, and payment, setup is prepared manually and expected in 10 minutes to 5 hours.
2
Copy and store it securely
Paste the delivered API key, base URL, and any newly created scoped key into your secret manager or deployment environment.
3
Watch usage by prefix
Use the key prefix and request logs to understand which service is sending traffic.
4
Rotate or revoke access
Replace stale credentials or revoke risky keys without deleting unrelated workspace access.
Authenticated request
curl https://unlimitedcodex.com/v1/chat/completions \
-H "Authorization: Bearer $UCX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.5",
"messages": [
{ "role": "user", "content": "Draft a customer reply." }
]
}'A clear handoff after checkout
Developers get a familiar Bearer-token flow with the delivered base URL, while operators get hashed storage, prefixes, lifecycle history, and the ability to cut off risky credentials quickly.
FAQ
Questions teams ask before rollout.
Do I get the API key instantly after checkout?
No. Setup is prepared manually after payment. Expected delivery is 10 minutes to 5 hours and includes the API key, base URL, setup files, activation date, start date, and end date.
Can I see an API key again after creation?
No. Full secrets are shown once. The dashboard keeps a display prefix so teams can identify the key safely.
What happens when I revoke a key?
Calls using that key stop working. Other keys in the workspace remain active unless you revoke them separately.
Can separate environments use separate keys?
Yes. Create distinct keys for local development, staging, production, or each service that sends API traffic.
Ready to build?