# ABBYY FineParser > Getting started, configuration, output formats, REST API, CLI, DocLang, plans, data privacy, support, and release notes for ABBYY FineParser, a self-hosted Docker container that parses documents into DocLang, JSON, or plain text for AI pipelines. > For the full ABBYY documentation index, see: https://docs.abbyy.com/llms.txt ## Getting Started - [Introduction](https://docs.abbyy.com/fine-parser/getting-started/introduction.md): What FineParser is: a self-hosted, CPU-only Docker container built on ABBYY FineReader Engine that returns a document's structure and text as DocLang, JSON, or plain text. - [Quickstart](https://docs.abbyy.com/fine-parser/getting-started/quickstart.md): Get a license file, start the container with docker run and FINEPARSER_LICENSE_DATA, confirm it with /healthz, then submit a document to POST /parse, poll the job, and download your first DocLang result with curl in under five minutes. - [AI coding agents](https://docs.abbyy.com/fine-parser/getting-started/ai-agents.md): Connect the ABBYY documentation MCP server to Claude Code or Codex so your agent can look up FineParser endpoints, parameters, and output formats while writing your integration. ## Basics - [Configuration](https://docs.abbyy.com/fine-parser/basics/configuration.md): Every setting as flag and environment variable (license, mode, language, listen address, output and scratch directories, job database, delete-on-download, upload limit and timeouts), the telemetry variables, how to confirm the license with /healthz, why recognition settings are fixed per container, the /app/output volume and one-container-per-volume rule, the 60 second stop timeout, port publishing, and the outbound license server requirement. - [Recognition modes](https://docs.abbyy.com/fine-parser/basics/recognition-modes.md): Choose between high-fidelity mode (text plus layout, tables, checkboxes, and reading order) and fast mode (text only) with the -mode flag. - [Languages](https://docs.abbyy.com/fine-parser/basics/languages.md): Set recognition languages with the -language flag, why fewer languages means faster and more accurate results, and the full table of 200+ language keys, programming languages, and special text types. - [Output formats](https://docs.abbyy.com/fine-parser/basics/output-formats.md): Choose DocLang, JSON, or plain text per submission with the outputType field, with cURL, Python, and Node.js examples, how the result file is named, and a comparison of what each format keeps. - [Licenses and plans](https://docs.abbyy.com/fine-parser/basics/licenses-and-plans.md): Register at fineparser.ai, pass your .fineparserlicense file in FINEPARSER_LICENSE_DATA, compare Free, Starter, Growth, Business, and Enterprise page allowances, manage your Stripe subscription, and what happens at the monthly limit. ## Concepts - [DocLang](https://docs.abbyy.com/fine-parser/concepts/doclang.md): The open, AI-native document format FineParser recommends: why it exists, how it encodes structure and bounding boxes in few tokens, an annotated example, file extensions, and links to the specification. - [REST API](https://docs.abbyy.com/fine-parser/concepts/rest-api.md): The asynchronous job API: submit a document to POST /parse (202 with a jobId), poll GET /jobs/{id} for pending, in-progress, successful, failed, or cancelled, download from GET /jobs/{id}/{name}, DELETE /jobs/{id}, and GET /healthz, with cURL, Python, and Node.js examples, every status code including 402/403/503 licensing refusals, result retention on the /app/output volume, DELETE_ON_DOWNLOAD, and restart and shutdown behavior. - [CLI](https://docs.abbyy.com/fine-parser/concepts/cli.md): Run the container as a one-shot command by passing input and output file paths as positional arguments alongside FINEPARSER_LICENSE_DATA, with the output format taken from the file extension (.doclang, .json, .txt). ## Reference - [FineParser Enterprise](https://docs.abbyy.com/fine-parser/reference/enterprise.md): The in-development Enterprise edition: unlimited pages, orchestrated throughput of 500+ pages per second, fully air-gapped deployment, engine tuning, marketplace availability, and how to express interest. - [FineReader Engine](https://docs.abbyy.com/fine-parser/reference/finereader-engine.md): How FineParser relates to the ABBYY FineReader Engine SDK it is built on, when the container is enough, and when to work with the engine directly for embedding, extra export formats, barcodes, ICR, classification, or full pipeline tuning. - [Data privacy and telemetry](https://docs.abbyy.com/fine-parser/reference/data-privacy.md): What leaves the container: license validation and OpenTelemetry usage telemetry (one job span plus seven metrics per job, with closed-set attributes for outcome, mode, doc_type, output_type, licensing decision, page count, and license key), what is never collected, how to print the stream to stdout or copy it to your own OTLP endpoint with FINEPARSER_OTLP_ENDPOINT, the unbilled-pages counter, and the IPv4 and IPv6 address ranges to allow for ABBYY's license server. - [Support and SLAs](https://docs.abbyy.com/fine-parser/reference/support.md): Community support on GitHub for every plan, ABBYY technical support for Business, and Enterprise SLAs. ## Release Notes - [1.0 Release Notes](https://docs.abbyy.com/fine-parser/release-notes/1.0.md): Features in the initial FineParser 1.0.0 release: POST /parse endpoint, DocLang/JSON/TXT output, two recognition modes, 200+ languages, and the CLI.