> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://cla-demo.postmansolutions.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://cla-demo.postmansolutions.com/_mcp/server.

# Welcome to CLA AutoExtract

AutoExtract (Fluxx) is CLA's event-driven platform for ingesting documents, classifying and splitting them, extracting structured data, and delivering results back to client applications.

#### [Platform](/platform)

Components, architecture, messaging topology and the individual microservices.

#### [Guides](/guides)

Client integration, upload API, error handling and the Documents AI user guide.

#### [API Reference](/api-reference)

Five services, one unified reference: File Intake, Registration, Extractor, Status Check and Document Splitter.

#### [Design & Research](/design)

HLDs, LLDs, spikes and architecture decisions behind the platform.

## The services at a glance

| Service                            | Role                                                                                                                 |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **File Intake**                    | Entry point for every file. Stores uploads, triggers malware scanning, and emits `accepted-file` events.             |
| **Registration**                   | Reference data per client application: allowed extensions, size limits, delivery routes, extractors and classifiers. |
| **Document Splitter / Classifier** | Determine document type and split compound files into individual documents.                                          |
| **Extractor**                      | Runs OCR / entity extraction jobs for a file and tracks job history.                                                 |
| **Status Check**                   | Audit trail and processing status for every file.                                                                    |
| **Postal**                         | Routes events to each client application's registered delivery endpoint.                                             |

## One API, one SDK

Although the platform is five independently deployed microservices, the OpenAPI definitions are merged into a **single API definition** so that a single SDK is generated. Each service becomes a namespaced sub-client. See the [SDK quickstart](/guides/getting-started/sdk-quickstart).

> **Note**
>
> All services authenticate with a JWT bearer token. Role and scope requirements per endpoint are described under [Guides](/guides).