Install Jentic One Beta

Connect the Parsio Document Parser API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Parsio Document Parser API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fparsio.io%2Fparsio" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fparsio.io%2Fparsio" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Parsio Document Parser API.

Create and manage email parsing mailboxes

Upload documents (PDFs, spreadsheets) for AI-powered parsing

Retrieve structured parsed data from documents and emails

Configure parsing templates and field extraction rules

Set up webhooks for real-time parsed data delivery

GET STARTED

Start building with Parsio Document Parser API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Parsio Document Parser API for, with concrete tasks.

★ Automated Invoice Data Extraction

Extract line items, totals, vendor details, and dates from PDF invoices using AI-powered parsing. POST /mailboxes/{mailbox_id}/documents uploads invoice PDFs, then GET /documents/{document_id}/parsed retrieves structured JSON with extracted fields. Configure webhooks via POST /mailboxes/{mailbox_id}/webhooks to push parsed data directly to accounting systems.

POST /mailboxes/{mailbox_id}/documents with PDF, then GET /documents/{document_id}/parsed to retrieve extracted invoice fields

Email Parsing and Lead Capture

Set up email parsing mailboxes that automatically extract structured data from incoming emails such as lead forms, order confirmations, or support tickets. GET /mailboxes lists all mailboxes with their parsing email addresses. Forward emails to the mailbox address, and Parsio extracts fields based on configured templates. Retrieve parsed data via GET /mailboxes/{mailbox_id}/documents.

GET /mailboxes to find parsing email address, forward emails to it, then GET /mailboxes/{mailbox_id}/documents to retrieve parsed data

Real-Time Document Processing via Webhooks

Configure webhooks to receive parsed document data as soon as parsing completes, enabling real-time automation. POST /mailboxes/{mailbox_id}/webhooks sets up webhook URLs, and Parsio POSTs parsed JSON to your endpoint immediately after processing. Ideal for triggering downstream workflows in CRMs, ERPs, or automation platforms.

POST /mailboxes/{mailbox_id}/webhooks with endpoint URL, then receive parsed data via webhook POST requests

AI-Driven Document Workflows via Jentic

An AI agent managing document workflows can upload invoices, parse order confirmations, extract table data from PDFs, and configure webhooks through Jentic without holding Parsio API keys in context. Jentic resolves intents like 'parse this invoice' to the correct Parsio upload and retrieval endpoints.

Search Jentic for 'parse a PDF document', load POST /mailboxes/{mailbox_id}/documents schema, execute upload, then retrieve parsed data

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for parsio api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/mailboxes

List all parsing mailboxes

GET

/mailboxes/{mailbox_id}

Retrieve mailbox details and configuration

POST

/mailboxes/{mailbox_id}/documents

Upload a document for parsing

GET

/mailboxes/{mailbox_id}/documents

List all parsed documents in a mailbox

GET

/documents/{document_id}/parsed

Retrieve parsed structured data from a document

POST

/mailboxes/{mailbox_id}/webhooks

Configure a webhook for real-time data delivery

POST

/mailboxes/{mailbox_id}

Update mailbox settings

GET

/mailboxes

List all parsing mailboxes

GET

/mailboxes/{mailbox_id}

Retrieve mailbox details and configuration

POST

/mailboxes/{mailbox_id}/documents

Upload a document for parsing

GET

/mailboxes/{mailbox_id}/documents

List all parsed documents in a mailbox

GET

/documents/{document_id}/parsed

Retrieve parsed structured data from a document

POST

/mailboxes/{mailbox_id}/webhooks

Configure a webhook for real-time data delivery

POST

/mailboxes/{mailbox_id}

Update mailbox settings

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Parsio Document Parser API by hand means learning its X-API-Key header auth, setting the api.parsio.io host, and building multipart upload and result-polling handling yourself. Through Jentic you install once, import Parsio from the API Directory, store the key once, and your agent calls it.

Permission scoping

Parsio puts the mailbox id in the URL path (/mailboxes/{mailbox_id}/...), so a rule can pin your agent to one mailbox: it can upload documents and read parsed data for that mailbox and nothing else. You choose the operations it may call, so webhook configuration is not included unless you add it.

Credential isolation

Your Parsio X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'parse a PDF invoice' or 'retrieve extracted email data', and Jentic returns the matching Parsio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Parsio Document Parser API through Jentic.

Why is there no official OpenAPI spec for Parsio API?

Parsio publishes API documentation at https://help.parsio.io/public-api but not a structured OpenAPI specification. Jentic generates and maintains this spec based on Parsio's documentation so that AI agents and developers can call Parsio API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Parsio API use?

The Parsio API uses API key authentication passed in the X-API-Key header. Retrieve your API key from your Parsio account settings. Through Jentic, the key lives in the encrypted vault and is injected at execution time so it never enters agent context.

What document types can Parsio parse?

Parsio can parse PDFs, emails (plain text and HTML), spreadsheets (CSV, Excel), and images (via OCR). The API accepts document uploads in these formats and returns structured JSON with extracted fields based on configured templates or AI-powered field detection.

How do webhooks work in Parsio?

Configure a webhook URL via POST /mailboxes/{mailbox_id}/webhooks, and Parsio will send a POST request with parsed JSON data to your endpoint immediately after a document is processed. Webhooks enable real-time automation without polling for results.

Can I customize what fields are extracted from documents?

Yes. Parsio supports template-based parsing where you define extraction rules and field mappings in the mailbox settings. The API also supports AI-powered auto-detection of common fields like invoices, receipts, and forms without manual template configuration.

What are the rate limits for the Parsio API?

Parsio's rate limits depend on your subscription plan. Standard plans support hundreds of documents per month with reasonable API request limits. Contact Parsio support for plan-specific rate limit details and enterprise volume pricing.

Can I limit what my agent is allowed to do with the Parsio Document Parser API?

Yes. Because your Jentic One instance is self-hosted, you write the rules that decide which Parsio operations and credentials your agent may use. Since Parsio puts the mailbox id in the URL path, such as /mailboxes/{mailbox_id}/documents, a rule can pin the agent to a single mailbox so it can only upload documents and read parsed data there. You also choose the operations it can call, so actions like configuring webhooks via POST /mailboxes/{mailbox_id}/webhooks stay off-limits unless you grant them.

Parsio Document Parser API

Name: Parsio Document Parser API
Brand: Parsio Document Parser API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring ObservabilityapiKey20 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Extract structured data from PDFs, emails, and documents; manage parsing mailboxes, retrieve parsed results, and configure webhooks across 20 endpoints.

Use for: Parse data from a PDF invoice, Extract structured information from an email, Set up a mailbox to automatically parse incoming emails, Retrieve all parsed documents from a specific mailbox

Not supported: Covers document upload, AI-powered parsing, parsed data retrieval, mailbox management, and webhook configuration. Does not handle document generation, OCR-only extraction, or batch processing outside mailbox workflows - use for structured data extraction from documents and emails only.

Jentic publishes the only available OpenAPI specification for Parsio API, keeping it validated and agent-ready. Parsio is an AI-powered document and email parser that extracts structured data from PDFs, emails, spreadsheets, and other documents. The API allows programmatic management of mailboxes, document upload for parsing, retrieval of parsed data, and webhook configuration for real-time data delivery, enabling automated document processing workflows.

Jentic One on Github View OpenAPI Document

Connect the Parsio Document Parser API to your agent

Capabilities

Start building with Parsio Document Parser API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Parsio Document Parser API