Codex CLI
Aikey365 implements the OpenAI Responses endpoint:
text
POST https://aikey365.com/v1/responsesThis can be used by Codex CLI versions that support a custom Responses provider.
Provider example
A user configuration commonly lives at ~/.codex/config.toml:
toml
model_provider = "aikey365"
model = "YOUR_MODEL_ID"
[model_providers.aikey365]
name = "Aikey365"
base_url = "https://aikey365.com/v1"
wire_api = "responses"
env_key = "AIKEY365_API_KEY"Then:
bash
export AIKEY365_API_KEY="sk-..."Codex configuration can evolve. If field names differ in your installed release, use the current official configuration reference.
Verify the API first
bash
curl https://aikey365.com/v1/responses \
-H "Authorization: Bearer $AIKEY365_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"YOUR_MODEL_ID","input":"Reply with OK"}'If curl works but Codex does not, inspect which provider, environment variable, Base URL, and config file the CLI actually loaded.