Clients and tools
Aikey365 can be used with SDKs, CLIs, and desktop clients that support custom API endpoints. The first step is to identify the wire protocol the client actually sends.
Protocol guide
| Client type | Typical protocol | Base URL |
|---|---|---|
| OpenAI SDK / compatible apps | Chat Completions / Responses | https://aikey365.com/v1 |
| Claude Code | Anthropic Messages | https://aikey365.com |
| Codex CLI custom provider | Responses | https://aikey365.com/v1 |
| Gemini ecosystem | Gemini v1beta | https://aikey365.com |
Standard setup flow
- Validate the key with curl.
- Fetch a current model ID.
- Confirm the client protocol.
- Configure Base URL, key, and model.
- Test in a new session with a minimal request.
- Add advanced features only after the basic path works.
Third-party software
Installation steps, user interfaces, and configuration fields can change between releases. Aikey365 documentation focuses on the stable API-side values rather than copying third-party screenshots.
Use a dedicated limited key for desktop tools and local development.