Skip to main content
Glama

Doxis AI.dp (Klippa DocHorizon) MCP by usefulapi

Submit a document for asynchronous capture

dochorizon_submit_async_capture

SPENDS CREDITS: queue one document for capturing and return a job_id right away; poll dochorizon_get_async_job, then read dochorizon_get_async_job_result. Use it for long documents and bursts (async jobs are not subject to the concurrent-request limit). No webhook or human review is configured. For identity, salary_slip and bank_statement the result holds personal data. Uses your own Doxis AI.dp (Klippa) credits: billed per request or per page depending on the service (extra components in a configuration can add cost), at your project's price (Billing → Pricing in the platform); a new account starts with EUR 25 of free credit. Give the document as exactly one of url (public https), data_base64 (small files) or file_id (a stored file). POST /document_capturing/v1/{model}/async.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic https URL of the document. Klippa downloads it (must complete within 30 seconds).
modelYesThe capturing model.
file_idNoA Doxis AI.dp storage file id (from dochorizon_upload_file or a toolkit result).
filenameNoA name for the file (helps content-type detection).
passwordNoPassword of a protected PDF. Only used for this request.
data_base64NoThe document as base64 (at most about 1.5 MB of file). Prefer url or file_id for anything bigger.
page_rangesNoPages to process, for example '1-3, 5', '2-last', 'first-last' (default: all pages; documents over 50 pages time out).
content_typeNoMIME type, if it cannot be detected.
configuration_slugNoSlug of a capturing configuration made in the platform (see dochorizon_list_configurations). Optional: the model's defaults apply without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.