Skip to main content
“Machina SDK” doesn’t refer to an installable package you pip install — it’s the name for the Client API: the REST API that runs on your project’s own pod. Confirmation straight from the source: api-reference/openapi.json’s info.title is literally "Machina Sports SDK". Every request is authenticated the same way as MCP and the CLI: an X-Api-Token header, scoped to your project.

​
What’s documented so far

Agent

Create, search, execute, and manage agents.

Workflow

Execute and schedule pipelines.

Document

Store and retrieve records, uploads, and generated files.

Skill

Create, search, execute, and manage packaged capabilities.

​
What isn’t documented yet — and why

machina-client-api’s own core/ directory has roughly 26 resource modules — far more than the 4 above. Its internal API_ENDPOINTS.md only documents Agent, Skill, Workflow, Execution, and Auth; it doesn’t cover the rest either, so the gap predates this revamp. This page does not claim the remaining modules (connector, mapping, prompt, retrieval, and others like vault, ledger, valora, socketio, tracking, worldcup, teams, favorite_team, newsletter, instance, dataset, content, scheduler, system, webhook, templates) are either public API surface or internal-only — that classification wasn’t done as part of this PR. Connector, Mapping, and Prompt are plausibly public (they have CLI commands and Studio UI — see connector, mapping, prompt), but publishing their API reference means reading each module’s routes/controller the same way this PR did for Skill, not assuming the shape from the CLI docs alone.
If you need one of the undocumented resources’ HTTP API today, don’t guess the shape from this page — read machina-client-api/core/<resource>/routes.py directly, or ask the team that owns it.
  • API Reference — the full endpoint list documented so far.
  • MCP and Machina CLI — the other two ways to talk to the same underlying API, authenticated the same way.