API/MCP

Access your agent programmatically through API requests. This is ideal for custom integrations, internal tools, or connecting your agent to your own applications and workflows.

You can still require users to be signed in and authenticated with a subscription, giving you the same access control and monetization options as any other deployment type.

---

It's an MCP endpoint too

The deployment type is called API/MCP because it gives you both. Alongside the REST examples, the deployment page has a Connect an MCP client panel: pick your client — Claude Code, Codex, Cursor, VS Code, or generic HTTP — copy the configuration, and this agent becomes a tool your AI client can call.

It authenticates with the deployment's own token, so a client set up this way can run this one agent and nothing else. That's the narrow alternative to the Pickaxe MCP Server, which exposes a whole workspace: use a deployment when you're giving someone one agent, and the workspace server when you're the one working.

---

Learn more

Full endpoint documentation, request bodies, and examples live in the Pickaxe API documentation.