> ## Documentation Index
> Fetch the complete documentation index at: https://docs.askactual.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat availability labels as authoritative. Do not present planned surfaces as live.
> The product MCP can act on Actual Jobs; the documentation MCP cannot.

# Availability

> Which Actual developer surfaces are available and which are planned.

## Available with this documentation site

* Public developer documentation at `docs.askactual.com` after deployment.
* Mintlify's documentation MCP at `docs.askactual.com/mcp` after deployment. It searches and retrieves these public pages and may submit documentation feedback.
* The idempotent `POST /v1/waitlist` API operation.

## Planned

* The canonical `/v1` HTTP Job API.
* Job create, read, revision, Approval, Evidence, events, and Recovery endpoints.
* Publication of `@actual/sdk-effect` and Speakeasy-generated TypeScript, Python, and Go SDKs.
* The authenticated product MCP at `mcp.askactual.com/mcp`.
* Product events and developer webhooks.

<Note>
  Examples for planned surfaces communicate intended semantics, not a release commitment. Endpoint
  paths, package names, event schemas, and authentication setup can change before release.
</Note>

An API operation becomes documented as available only after the compatible server is deployed and its contract is published. Generated SDKs and API reference material follow that server release.