Developer overview
Two ways to use XPlor3 from outside the studio, MCP for AI agents and the REST API for your app, with one API key.
Everything the studio console can do, from picking a model to downloading the result, can be done from outside the studio. You choose the way in by who is calling.
| MCP | REST API | |
|---|---|---|
| For | AI agents: Claude Desktop, Cursor, local agents | Apps, backends, automation scripts |
| Address | https://mcp.xplor3.space/mcp | https://api.xplor3.space/v1 |
| How it is called | The agent picks tools itself from the conversation | You send HTTP requests |
| Key | Header Authorization: Bearer xpk_... | Header Authorization: Bearer xpk_... |
| Knowing a job ended | The wait_for_generation tool, one call | A webhook to your server, or Server-Sent Events |
Both use the same key, made on the studio's Credentials page.
What both have in common
- The same balance and rates. Generations over MCP or REST take from your account balance at exactly the same rates as the studio. Failed results refund their own credits.
- The same history. Jobs started through the API appear in the studio's History, and the other way round.
- New models are available at once. The catalogue is read when it is called, so a newly added model can be used without updating anything on your side.
- A verified email is needed to start a generation.
Get started
1. Make a key
API keys are made in the studio and shown only once.
2a. Connect an agent
Paste the configuration into an MCP client, then ask the agent for an image.
2b. Call it from code
The generation flow over REST, from the first request to downloading the file.
3. Build a model's input
The modelSlug, fields, accepted values and rules of every model.