Quickstart

Every Machina project is reachable four ways. They all talk to the same project, authenticate with the same project-scoped X-Api-Token, and see the same agents, workflows, skills, and documents — pick the one that matches where you're working, and switch whenever you like.

Path	Best for	Start here
MCP	Coding agents — Claude Code, Cursor, Codex, Claude Desktop, SportsClaw	Connecting External Agents
CLI	Your terminal, scripts, and CI pipelines	CLI Quickstart
API	HTTP integrations from your own backend or app	Machina API
Studio	Configuring and inspecting your project in the browser	Get access to Studio

You need a project before any of them. If you don't have one yet, create it in Studio first — it takes a minute and provisions itself.

MCP — for coding agents

Your project exposes an MCP endpoint that any MCP-capable client can connect to. With the CLI installed and signed in, it resolves the URL and mints a token for it:

machina connect --probe                      # resolve + verify, token masked
machina connect <project-id> --mint --reveal  # durable dedicated key, revealed

Then paste the client-specific snippet from Connecting External Agents — it covers Claude Code, Cursor, Codex, Claude Desktop, and any other MCP client. See the MCP Overview for what the endpoint exposes.

CLI — for your terminal and CI

Install the CLI, then sign in and pick a default org and project:

machina login
machina org use <org-id>
machina project use <project-id>

The CLI Quickstart takes it from there to your first workflow run. For CI or headless environments, use an API key instead of machina login — see Authentication.

API — for HTTP integrations

The Machina API is a REST API on your project's own pod — there's no client library to install. Create an API key, then send it on every request:

curl --request POST \
  --url https://{api-address}.org.machina.gg/agent \
  --header 'Content-Type: application/json' \
  --header 'x-api-token: <api-key>' \
  --data '{}'

API Schemas covers headers, filtering, and pagination; the endpoint reference covers Agent, Document, Workflow, and Skill.

Studio — in the browser

Machina Studio is where you create projects and configure and inspect everything in them. Follow the Studio quickstart in order:

1. Get access — sign up and create your first project.
2. Integrate data — install a connector.
3. Deploy — what provisioning does for you.

Each project's own Quickstart page in Studio also shows its API credentials, code snippets, and an MCP install shortcut.

Not documented yet

Coming with the Agent-first DX work, across MCP, CLI, and API: durably retrievable execution results (DX-04), typed evaluations (DX-05), and model-route evidence from the AI Router (DX-06). This page will link to them once they're released; until then, only the commands and endpoints documented here are supported.