Skip to main content
Both SDKs give you a fluent builder over the typed workflow graph, a Workflow handle to upload and run documents, a Run handle to wait on, and a typed Result. They target API v3: flat run reads, document packet handles, keyset pagination, and idempotent upload and run triggers.
The 1.0 SDKs are release candidates: Python 1.0.0rc1 and TypeScript 1.0.0-rc.1. The stable 0.x packages keep using v2 during its deprecation window. Upgrading needs code changes; follow the 0.x to 1.0 migration guide.

​
Install

Both clients take the API key explicitly: Client(api_key="af_...") and new Anyformat({ apiKey: "af_..." }). See Authentication.

​
Pick your surface

Python SDK

Sync and async clients, the builder, results with drawn layout boxes, knowledge ask, evals.

TypeScript SDK

The same builder and handles for Node.js 18+, with generated wire types.

Command line (afx)

Parse, extract, run and manage workflows from a shell. Installed with the Python package.

MCP server

Give Claude Code, Cursor or any MCP host anyformat as tools.

Coding assistant

The Claude Code skill with the design know-how; the verbs come from the MCP server or the API reference.

Raw HTTP

Every endpoint page has copy-paste examples. Start with upload and run.

​
The same graph everywhere

A workflow built with either SDK, the CLI, Studio or the MCP server is the same typed graph of nodes and edges. The node schemas page lists every field each node accepts; each builder method maps onto one node.