Approved changes to Cogneris product surfaces, APIs, schemas, models, and documentation, with impact and migration guidance.
2026
Monthly overage cap on Pro and Scale
Impact
Pro and Scale subscriptions now carry a monthly overage cap: 100 in the subscription's currency (€100 in the EU region, $100 in the US region) by default, adjustable by a company admin up to 10,000 in the console. A request that would take the period's overage past the cap is refused with HTTP 402 and the reason BILLING_OVERAGE_CAP_REACHED; reaching the cap exactly is allowed. Company admins receive an e-mail at 80% and at 100% of the included credits and of the cap, once per period.
Migration
No change to existing integrations is required. Clients that run high volume on Pro or Scale should handle HTTP 402 with reason BILLING_OVERAGE_CAP_REACHED by raising the cap in the console or waiting for the next billing period.
Compatibility
Credit prices, plan allowances and overage rates are unchanged. Free, Unlimited and Enterprise are not affected: Free still stops at zero credits, and the post-paid plans have no cap.
Deprecations
Nothing is deprecated. Uncapped overage on Pro and Scale is replaced by the capped behaviour above.
Rollout and rollback
Shipped in the billing-be release 2026.10.27.001, serving the EU production region since 2026-10-27; the US region is paused. Rollback is a redeploy of the previous billing-be release, which restores uncapped overage; the cap and the alerts are additive and need no data migration back.
Evidence
Pricing: how credits work and the console's Billing screen, which shows the cap and the overage spent in the period.
Document fraud verification routes
Impact
POST /api/v1/fraud-verify analyses a document for signs of tampering or reuse and returns a request id; GET /api/v1/fraud-verify/{requestId} returns the result. The routes are enabled per tenant on request and cost 8 credits per analysis; the scopes fraud-verify.write and fraud-verify.read gate the two calls.
Migration
None for existing integrations: the routes are additive. To use them, request enablement for your tenant and create an API key carrying the fraud-verify scopes; a call on a tenant without enablement returns fraud.not_enabled.
Compatibility
Existing routes, envelopes and field shapes are unchanged. The published OpenAPI contract moved to version 2026-10-23 to carry the new routes.
Deprecations
Nothing is deprecated.
Rollout and rollback
Shipped in the api-be and billing-be releases 2026.10.27.001 in the EU production region. Rollback is a redeploy of the previous releases: the routes disappear and no stored data needs migration.
The published OpenAPI document is version 2026-10-23. It adds the fraud verification routes, documents that asynchronous extraction jobs post-process dates, numbers and tables the same way as a synchronous extraction, and announces that API keys created through the API will require an expiry on a date to be published in the documentation release notes.
Migration
None today. To prepare for the key-expiry change, send an expiry and the scopes you need when you create a key through the API; keys created on the Developers screen already require both.
Compatibility
No existing route, envelope or field shape changed. A key created through the API without an expiry still gets full access and never expires until the announced date.
Deprecations
The no-expiry default for API-created keys is scheduled for removal; the date will be announced in the documentation release notes before it takes effect.
Rollout and rollback
The contract ships with the static site and rolls back with the corresponding site revision; the service behind it is the api-be release 2026.10.27.001.
Cogneris runs a Model Context Protocol server at https://mcp-eu.cogneris.ai/ (stateless streamable HTTP). From VS Code, Cursor, Claude Code or any MCP client, an assistant can search the documentation and the API reference, create API keys and webhook endpoints, train classifiers, run workflows and Build AI, and fill PDFs — on your tenant, with the same metering and audit trail as the REST API. 53 tools across eight areas; a developer token generated in the console (30 or 90 days) or an OAuth 2.1 sign-in authenticates the session.
Migration
None. The server is additive; REST integrations are unaffected.
Compatibility
Tool calls reach the same services as the REST API and spend the same credits. API keys created through the server never carry the apikeys.manage, mcp.read or mcp.write scopes.
Deprecations
Nothing is deprecated.
Rollout and rollback
Serving in the EU production region (mcp-be release 2026.10.27.001; developer tokens and the 401 with resource_metadata since 2026-10-20). The US host is provisioned but the region is paused. Rollback is a redeploy of the previous mcp-be release; nothing in the REST API depends on it.
Build AI: from a described document type to a draft setup
Impact
Build AI turns a described document type into a draft extraction setup: clarifying questions (2 credits per call), market research (10), a build plan (10) and plan revisions (5). It runs from the Vision console and from the MCP server's builder tools.
Migration
None; the feature is additive and opt-in per use.
Compatibility
Credits are spent from the same pool as every other operation; the four prices are on the pricing page. The REST routes under /api/v1/builder/sessions exist but are not yet part of the published OpenAPI contract and may change before they are.
Deprecations
Nothing is deprecated.
Rollout and rollback
Shipped in vision-be (2026.10.29.001), api-be and billing-be (2026.10.27.001) in the EU production region. Rollback is a redeploy of the previous releases; draft setups created by Build AI remain ordinary templates and are unaffected.
Client SDKs on npm, PyPI, NuGet.org and Maven Central
Impact
Client SDKs for TypeScript (@cogneris-ai/document-ai-sdk, with the @cogneris-ai/document-ai-cli CLI), Python (cogneris-document-ai-sdk), .NET (Cogneris.DocumentAI, .NET 8) and Java (ai.cogneris:cogneris-document-ai-sdk, Java 17) are published: 0.1.0 on all four registries on 2026-09-21, and 0.2.0 on npm and PyPI on 2026-09-30.
Migration
None; the REST API works without an SDK. Projects consuming local artifacts can switch to the registry packages at the same versions.
Compatibility
0.2.0 is generated from the OpenAPI contract of 2026-09-28 and corrects a compatibility summary; see VERSIONING.md in the repository. The committed source is 1.0.0 and is not published.
Deprecations
Nothing is deprecated. There is no Go or mobile client.
Rollout and rollback
Published through the repository's release workflow (npm, PyPI) and owner-controlled publication (NuGet.org, Maven Central). Rollback of a faulty package is publishing a corrected version: registry versions are immutable and the previous one stays installable.
The Scale plan is available: €499 per month (US region: $499) for 40,000 credits, with overage at €0.01 per credit — the lowest self-serve rate per credit.
Migration
None. Pro subscriptions can upgrade at any time; the prorated difference is charged on the next invoice.
Compatibility
Free, Pro, Unlimited and Enterprise are unchanged.
Deprecations
Nothing is deprecated.
Rollout and rollback
Seeded in billing-be on 2026-09-29 and serving in the EU production region. Rollback is deactivating the plan in the catalogue; existing Scale subscriptions keep their terms until changed.
