Veryfi OCR API

Name: Veryfi OCR API
Brand: Veryfi OCR API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey17 EndpointsREST

For Agents

Programmatically process document, list documents. Covers 17 operations with apiKey authentication.

Install Jentic One Beta

Connect the Veryfi OCR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Veryfi OCR 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Veryfi OCR API.

Process Document

List Documents

Get Document

Update Document

GET STARTED

Start building with Veryfi OCR API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Veryfi OCR API for, with concrete tasks.

★ Payments Operations

Use the Veryfi OCR API to perform payments operations programmatically. The API provides 17 endpoints covering core functionality including process document, list documents, get document.

Call POST /documents to process document

Automated Documents Management

Automate documents operations by combining multiple Veryfi OCR API endpoints. Agents can list documents and then get document in a single workflow.

Call GET /documents to list documents, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Veryfi OCR API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'process document', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

17 endpoints — veryfi ocr api provides multi-modal data extraction from receipts, invoices, business cards, checks, contracts, tax forms, bank statements, and other documents.

METHOD

PATH

DESCRIPTION

POST

/documents

Process Document

GET

/documents

List Documents

GET

/documents/{document_id}

Get Document

PUT

/documents/{document_id}

Update Document

DELETE

/documents/{document_id}

Delete Document

POST

/documents/{document_id}/line-items

Add Line Item

GET

/documents/{document_id}/line-items

List Line Items

DELETE

/documents/{document_id}/line-items

Delete All Line Items

POST

/documents

Process Document

GET

/documents

List Documents

GET

/documents/{document_id}

Get Document

PUT

/documents/{document_id}

Update Document

DELETE

/documents/{document_id}

Delete Document

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Veryfi client id and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'process a receipt document' or 'read line items from an invoice', and Jentic returns the matching Veryfi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Veryfi OCR API through Jentic.

What authentication does the Veryfi OCR API use?

The Veryfi OCR API uses an API key passed in the `CLIENT-ID` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I process document with the Veryfi OCR API?

Yes. Use the POST /documents endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Veryfi OCR API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I process document through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'process document'. Jentic returns the matching Veryfi OCR API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Veryfi OCR API have?

The Veryfi OCR API exposes 17 endpoints covering documents, line items, tags operations.

Can I limit what my agent is allowed to do with the Veryfi OCR API?

Yes. Jentic One is self-hosted, so your own rules decide which Veryfi operations and credentials the agent may use. Because the document id sits in the URL path (/documents/{document_id}), you can pin the agent to a single document and only the operations you approve, such as POST /documents to process a document or GET /documents to list them. Destructive calls like DELETE /documents/{document_id} or deleting a document's line items stay off unless you explicitly grant them.

Veryfi OCR API

Connect the Veryfi OCR API to your agent

Capabilities

Start building with Veryfi OCR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs