Zuva
Zuva (by Kira Systems) provides a contract and document AI REST API for extracting structured data from unstructured documents. The Zuva DocAI API offers asynchronous OCR, field extraction across 1,400+ pre-built fields, multi-level document classification across 220+ document types, language detection, and a searchable fields catalog, secured with Bearer API tokens across US and EU regions.
Zuva publishes 5 APIs on the APIs.io network, including Classification API, Field Extraction API, Fields API, and 2 more. Tagged areas include Artificial Intelligence, Document AI, Contract Analysis, Field Extraction, and Classification.
Zuva’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.
Kin Score
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
Zuva Classification API
Multi-level document classification.
Zuva Field Extraction API
Extract field values from documents.
Zuva Fields API
Field catalog management.
Zuva Files API
Upload and manage document files.
Zuva OCR API
Optical character recognition.
Open Collections 7
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONZuva DocAI Classification API
OPEN COLLECTIONZuva DocAI Classification Field Extraction API
OPEN COLLECTIONZuva DocAI Classification Fields API
OPEN COLLECTIONZuva DocAI Classification Files API
OPEN COLLECTIONZuva DocAI Classification OCR API
OPEN COLLECTIONZuva DocAI API
OPEN COLLECTIONScroll for all 7
Pricing Plans 1
Published pricing tiers and plan structures.
Zuva Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Zuva Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Zuva Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/zuva"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/zuva/operations?limit=25"
curl "https://apis.io/api/v1/providers/zuva/evidence"
Discovery needs no key. Ratings and market analysis are Pro.