Skip to main content
Use the REST API to save a catalog model, submit a run, cancel it, and read its records. Manage billing and members in the dashboard. A run is one task you send to Millwork; the API calls it an execution. Every live run has a platform fee, charged when Millwork accepts the run; model usage is a separate cost. Read Model access and billing for what you pay and when.
Send a Millwork API key as a bearer token. Send a request key in the Idempotency-Key header with every run, so a retry does not start the work twice. API basics covers both.

​
Developer interfaces

Use the TypeScript SDK or Python client from your code, or connect the execution MCP to a coding assistant. The REST API is available directly when you want to send HTTP requests yourself.
The documentation MCP searches and reads these docs. It also offers submit_feedback for documentation feedback; review the message before your assistant sends it. It cannot access your organization. Use the execution MCP to work with your models and runs.

​
Output-check capabilities

Bring any verifier logic. An output check applies your rules to a candidate answer; the API calls it a verifier. Put a policy evaluator, model, proof engine, or completed workflow result behind one endpoint. Your service makes the check; Millwork records its verdict, quality score, and optional named results with the governed run. Named results are your service’s claims; use evidence the graded agent cannot alter if those claims need independent proof. Start with the Cookbook chooser, then follow Connect an output check for the shared local test, connection, approval, and receipt path. The interfaces below are other ways to reach that same path. The verifier-dock contract owns the check endpoint’s request and response shape. Capabilities are release-specific: use millwork verifier capabilities --json for the installed CLI, or inspect the installed SDK operation catalog or MCP tools/list before acting.

​
Ask these docs from a coding assistant

Give your coding assistant a page with Copy page or View as Markdown. Use a coding assistant explains this workflow. An assistant with the documentation MCP connected can also search and read these docs. It has no access to your organization, runs, or keys.

​
Models Millwork provides

Use one Millwork API key to run models from your organization’s catalog. Millwork manages their provider connections and charges model usage to your Millwork credit. Run millwork models list or read GET /v1/model-catalog to see the models available to you.

​
Providers you can connect

Run millwork provider list to see available providers and your existing connections. Choose a provider before getting a key. OpenRouter uses browser approval; other enabled providers use private browser key entry. For the providers and sign-in methods available to your organization, read GET /v1/model-source-profiles. Use only the returned providers and follow Connect a provider account for the matching setup method. The API auth scheme describes the resulting credential; OpenRouter’s api_key scheme still uses browser approval. GET /v1/model-catalog lists catalog models available to your organization. A provider’s name in a reference example does not mean its connection is available on your account. To replace access or disconnect an existing connection, follow Rotate or revoke a connection. With your provider account, the provider bills model usage and Millwork charges the platform fee. For a model Millwork provides, both come from Millwork credit. Review the fee and model allowance before approving a run; Model access and billing explains the two charges.

Connect a provider account

Find a provider your organization can connect and follow its setup method.

Make your first API call

Send a free test run and read its receipt.