Tool integrations
Use your AI526 API key and public model ID in a client that accepts a custom API connection. Match the protocol before entering its URL.
Start with standard API setup: OpenAI / Anthropic. Clients with a custom URL setting usually need only a URL, key and model ID.
Choose a tool
| Tool | Current status | Guide |
|---|---|---|
| WorkBuddy desktop | Custom API supported by its documentation; Chat Completions setup has not been tested end to end | Set up WorkBuddy |
| Codex CLI / desktop | Custom providers supported; AI526 currently lacks the required Responses endpoint | Codex compatibility |
| Doubao desktop | Third-party Base URL / API key support has not been verified | Desktop compatibility |
| OpenClaw | Existing separate guide | OpenClaw setup |
Connection details
- Create an API key in the dashboard and save it when shown.
- Copy a public model ID from the model catalog. Check the capabilities your task needs, including tools and image input.
- The OpenAI-compatible base URL is
https://api.ai526.com/v1. The full Chat Completions URL ishttps://api.ai526.com/v1/chat/completions. - Replace
YOUR_AI526_API_KEYin examples with your own key; it is a placeholder.
API requests follow AI526 billing rules. Client subscriptions are separate. Automated tasks can make multiple requests; begin with a short task and review its usage.
Protocols and verification
These guides configure model API connections. MCP connects tools and does not convert a Chat Completions endpoint into a Responses endpoint.
After receiving an answer, check the model ID, status and usage in your AI526 request history. Test images, tools and follow-up turns separately when needed. When reporting a failure, include the error code and request ID, never your full API key.
Official sources reviewed on 2026-10-28. Each guide links its sources. No live, billable client calls were performed.