This 18-minute demo shows you two ways to integrate generative AI into your document processing pipeline.
Supercharge AI automation with the power of reliable, accurate OCR
Increase straight-through document processing with data-driven insights
Integrate reliable Document AI in your automation workflows with just a few lines of code
PROCESS UNDERSTANDING
PROCESS OPTIMIZATION
Purpose-built AI for limitless automation.
Kick-start your automation with pre-trained AI extraction models.
Meet our contributors, explore assets, and more.
BY INDUSTRY
BY BUSINESS PROCESS
BY TECHNOLOGY
Build
Integrate advanced text recognition into your applications via API.
Production-grade document parsing infrastructure for AI workflows.
AI-ready document data for context grounded GenAI output with RAG.
Explore purpose-built AI for Intelligent Automation.
Grow
Connect with peers and experienced OCR, IDP, and AI professionals.
A distinguished title awarded to developers who demonstrate exceptional expertise in ABBYY AI.
Explore
Insights
Services
November 11, 2026
Large language models (LLMs) have changed what teams expect from document automation. But plugging an LLM into a real business process is not as simple as pasting a prompt into a chat window. You need control over which model runs, where your data goes, and how it all fits into a governed pipeline.
The ABBYY Document AI platform now lets you connect your own LLM directly to your document processing workflows, so you can pair ABBYY's document expertise with the generative model that best suits your needs. Here is how it works.
Key takeaways
Jump to:
Supported LLM providers and connections
How to set up an LLM connection within your IDP pipeline
Demo video: How to set up a connection
Where LLM connections are used
You bring the model; the platform handles the integration. Right now, you can connect five LLM providers natively through Connections, and access a sixth as an ABBYY-managed option:
| Provider | Example models |
| Anthropic | claude-opus-4-5, claude-sonnet-4-5 |
| Google AI Studio (Gemini) | gemini-2.0-flash, gemini-2.5-pro |
| Microsoft Foundry | gpt-4, gpt-4.1-nano, gpt-35-turbo |
| Mistral AI | mistral-large-latest, mistral-small-latest |
| OpenAI ChatGPT | gpt-4, gpt-3.5-turbo |
| PHOENIX Plus | ABBYY selects and maintains the model |
How to choose which LLM to use:
We are actively working on expanding the list of supported models (including proprietary and self-hosted models) to be able to serve the needs of all our customers.
Connecting a model takes just a couple of minutes and no code. You will need administrator access to Configuration and valid API credentials from your provider. Here is the six-step process:
Because connections live at the tenant level, your whole team can reuse them. Tenant administrators can also override the default connection per environment without republishing a skill.
For more information on how to set up an LLM connection in your Vantage tenant, visit the documentation.
Once your connection is live, you can put it to work inside the Prompt-based Extraction activity in Advanced Designer. This is where a connected LLM helps you extract data from documents using natural language instructions.
We covered that feature in depth in its own Feature spotlight article: "Prompt-Based Extraction: How to Use LLMs Within Your Governed Document Processing Pipeline"
Not every model sits on the native provider list yet. If your organization runs a proprietary, self-hosted, or otherwise unsupported LLM, you can still connect it today through the Custom Activity.
A Custom Activity collects document data from a transaction and sends it to any external system over an HTTP request, using a script you configure. The response comes back and saves to the transaction data. In practice, that means you can:
The Custom Activity requires a secure SSL connection, and you can place it inside a For Each Document activity to process one document at a time.
LLM Connectivity gives you real flexibility from day one: native support for leading providers, a quick setup, and a script-based path for everything else. And we are just getting started.
ABBYY is actively expanding native LLM provider support, including proprietary and self-managed models, with more integrations on the way. Until those land natively, the Custom Activity bridges the gap, so you never have to wait to connect the model your workflow depends on.
Ready to connect your first model? Head to Configuration > Connections in Vantage and add a connection today.
Discover the full potential of the ABBYY Document AI platform and explore all of its robust capabilities by visiting abbyy.com/ai-document-processing/.
The platform natively supports five LLM providers through Connections: Anthropic, Google AI Studio (Gemini), Microsoft Foundry, Mistral AI, and OpenAI. You supply your own API credentials and model name for each. In addition, PHOENIX Plus is available as an ABBYY-managed connection: ABBYY provisions and operates the model on your behalf, so no API key, endpoint URL, or model selection is required on your side. Other models, including proprietary and self-hosted LLMs, can be connected today through the Custom Activity.
BYOM lets you connect the large language model of your choice to your document processing workflows rather than being locked into a single vendor's model. In the ABBYY Document AI platform, this means you keep control over which model runs, its cost, and how your data is handled, while still benefiting from ABBYY's document expertise.
Use the Custom Activity in the process skill designer. It sends selected document text, fields, and images to any external HTTP endpoint using a script, then saves the response back to the transaction. This lets you connect proprietary or self-hosted models that are not yet on the native provider list. The endpoint must support a secure SSL connection.
Where your document data is processed depends on the provider you choose. With OpenAI ChatGPT, data is processed on OpenAI's infrastructure under its terms and policies. With Google AI Studio (Gemini), data is processed on Google's infrastructure. Microsoft Foundry is the best fit when you need data-residency controls or Azure integration, since it runs on Microsoft's Azure infrastructure. With PHOENIX Plus, data is processed within the same environment as Vantage; see [data handling and security] for full details. For full data control, the Custom Activity lets you send data only to your own endpoint.