Actual developer documentation

Actual lets a person state an Objective—the physical state they want—and coordinates a durable Job toward a verified Outcome. The User controls authority; Actual owns coordination.

The public Job API, SDKs, and product MCP described here are planned developer surfaces unless a page explicitly marks a feature Available. Do not build production integrations against planned endpoints yet.

Start with the quickstart

Learn the intended integration flow without mistaking target examples for a live API.

Understand Jobs

Follow an Objective through authority, execution, Verification, and Recovery.

Choose an SDK

Compare Actual’s Effect client with Speakeasy-generated clients.

Choose the right MCP

Product actions and documentation search use separate servers.

The completion rule

A booking, payment, Provider acceptance, tool result, or model claim is not an Outcome. Actual only completes a Job after Evidence is evaluated successfully by Verification.

Public surfaces

Surface	Purpose	Availability
HTTP API at `api.askactual.com/v1`	Canonical programmatic Job interface	Planned
Product MCP at `mcp.askactual.com/mcp`	Authenticated Actual product actions	Planned
SDKs	Effect-native and generated API clients	Planned
Docs MCP at `docs.askactual.com/mcp`	Search public docs and submit documentation feedback	Available with the hosted docs site

See availability before implementing an integration.

Last modified on August 13, 2026

⌘I

Get started

Concepts

Guides

SDKs

Start with the quickstart

Understand Jobs

Choose an SDK

Choose the right MCP

The completion rule

Public surfaces

Start with the quickstart

Understand Jobs

Choose an SDK

Choose the right MCP

​The completion rule

​Public surfaces

The completion rule

Public surfaces