# DocAI Fabric

> https://app.docaifabric.com runs DocAI Fabric prod-us-2026.10.16-3, the hosted service (SaaS). DocAI Fabric processes documents: a project defines document classes, the fields to extract from each, validation rules and a processing workflow; transactions are batches of documents run through a project.

This page is for AI agents. It says which way to work with this deployment for each job. When your user's job is not clear, ask them.

## Which way for which job

- Configure a project (classes, fields, rules, workflow, catalogs, connectors, exports): MCP.
- Submit documents, follow transactions to the end, fetch their results, hand a transaction to a person for review: MCP.
- Review transactions as an agent at an Agent Review step: MCP, with an integration API key your user creates for it.
- Your client has no MCP, or you are writing a fixed integration: the REST API.

Prefer MCP. Its tools check your permissions and keep the guardrails (changes go to a draft until someone publishes, anything destructive asks for confirmation), and it serves playbooks written for this version.

## Connect over MCP

Server URL: `https://app.docaifabric.com/mcp` (Streamable HTTP). Your user signs in to DocAI Fabric in the browser and approves the connection; you then act as that person, with their permissions.

Claude Code (then run `/mcp`, choose docaifabric, and your user signs in):

```bash
claude mcp add --scope user --transport http docaifabric https://app.docaifabric.com/mcp
```

OpenAI Codex:

```bash
codex mcp add docaifabric --url https://app.docaifabric.com/mcp
codex mcp login docaifabric
```

Claude on the web, Claude Desktop and Cowork: your user adds a custom connector with the server URL under Settings > Connectors, leaving Advanced settings empty.

Automation with nobody to sign in: your user creates an API key on the Agents & API page and passes it through the environment; send it as the `X-API-Key` header or as a bearer token, for example:

```bash
claude mcp add --scope user --transport http docaifabric https://app.docaifabric.com/mcp \
  --header "X-API-Key: $DOCAIFABRIC_API_KEY"
```

Once connected, call `list_skills` and read the skill for the job before you act.

Details: https://app.docaifabric.com/docs/api/agents

## REST API

OpenAPI: https://app.docaifabric.com/openapi.json; interactive reference: https://app.docaifabric.com/api-docs. Authenticate with an API key in the `X-API-Key` header. Guide: https://app.docaifabric.com/docs/api/overview

REST has fewer guardrails than MCP: confirm deletes, publishing to production and production submissions with your user first.

## Documentation

https://app.docaifabric.com/docs/ (user guide and API reference). Over MCP, `grep_documentation` and `read_documentation` search the same documentation.

## Rules

- Ask your user for credentials. Never put a secret on a command line or in the conversation: use environment variables, or let the CLI prompt for it.
- Before anything that deletes, publishes to production or cannot be undone, ask your user.