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 API contracts indexed 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.

The Zuva catalog on APIs.io includes 1 Spectral governance ruleset.

Zuva’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.1/100 emerging ▬ flat Agent 19/100 agent aware Front door AI 5/6 prominent Heartbeat 67/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumOpen⚡ Free to try

1 published contract

Artificial Intelligence Document AI Contract Analysis Field-Extraction Classification OCR

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 26.1/100 · emerging

Contract Quality 8.3 / 19

Developer Ergonomics 4.7 / 15

Access Clarity 1.0 / 15

Operational Transparency 1.2 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 0.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/zuva/"><img src="https://apis.io/badge/zuva/card.svg" alt="Zuva on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 6.4 — up to +18.7 composite points Ask about this →
Contract Quality scores 44.1 — up to +14.0 composite points Ask about this →
Developer Ergonomics scores 31.0 — up to +13.8 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/zuva/apis.yml: open an issue on github.com/api-evangelist/zuva to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
RPA and Document AI (RPA marketplaces, intelligent document processing)	builds-on	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

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 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Zuva DocAI Classification API

OPEN COLLECTION

Zuva DocAI Classification Field Extraction API

OPEN COLLECTION

Zuva DocAI Classification Fields API

OPEN COLLECTION

Zuva DocAI Classification Files API

OPEN COLLECTION

Zuva DocAI Classification OCR API

OPEN COLLECTION

Zuva DocAI API

OPEN COLLECTION

Zuva API pricing

Not yet checked against Zuva's own pricing page. Compiled by API Evangelist on 2026-06-21 from zuva.ai/pricing/; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free Developer Tier free	—
Pay-as-you-go usage	—
Enterprise / Custom enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Files Per Day: 25 files
Free Tier Extractions Per Day: 25 extractions
Free Tier Classifications Per Day: 25 classifications

Compiled by API Evangelist, not yet checked against Zuva's documentation. All 6 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Zuva Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Zuva Rate Limits

6 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Zuva Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Zuva API Rules

63 rules · 58 error-severity 2 warn-severity 3 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zuva Authentication

http · 1 scheme

SECURITY

Zuva Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Zuva Agentic Access

22 operations · 9 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Source (apis.yml)

aid: zuva
url: https://raw.githubusercontent.com/api-evangelist/zuva/refs/heads/main/apis.yml
name: Zuva
kind: company
description: 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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: open
  trial: false
  try_now: true
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Open access
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zuva.png
tags:
- Artificial Intelligence
- Document AI
- Contract Analysis
- Field-Extraction
- Classification
- OCR
tags_raw:
- AI
- Document AI
- Contract Analysis
- Field Extraction
- Classification
- OCR
created: '2026-06-21'
modified: '2026-06-21'
specificationVersion: '0.23'
apis:
- aid: zuva:zuva-classification-api
  name: Zuva Classification API
  description: Multi-level document classification.
  humanURL: https://zuva.ai/documentation/services/file-submission/
  baseURL: https://us.app.zuva.ai/api/v2
  tags:
  - Classification
  properties:
  - type: OpenAPI
    url: openapi/zuva-classification-api-openapi.yml
  - type: Documentation
    url: https://zuva.ai/documentation/services/file-submission/
  - type: APIReference
    url: https://api-reference.zuva.ai/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/field-extraction-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/classification-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/services/language-classification/
  - type: Documentation
    url: https://zuva.ai/documentation/services/using-ocr/
  - type: Documentation
    url: https://zuva.ai/documentation/services/field-extraction/
- aid: zuva:zuva-field-extraction-api
  name: Zuva Field Extraction API
  description: Extract field values from documents.
  humanURL: https://zuva.ai/documentation/services/file-submission/
  baseURL: https://us.app.zuva.ai/api/v2
  tags:
  - Field-Extraction
  tags_raw:
  - Field Extraction
  properties:
  - type: OpenAPI
    url: openapi/zuva-field-extraction-api-openapi.yml
  - type: Documentation
    url: https://zuva.ai/documentation/services/file-submission/
  - type: APIReference
    url: https://api-reference.zuva.ai/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/field-extraction-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/classification-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/services/language-classification/
  - type: Documentation
    url: https://zuva.ai/documentation/services/using-ocr/
  - type: Documentation
    url: https://zuva.ai/documentation/services/field-extraction/
- aid: zuva:zuva-fields-api
  name: Zuva Fields API
  description: Field catalog management.
  humanURL: https://zuva.ai/documentation/services/file-submission/
  baseURL: https://us.app.zuva.ai/api/v2
  tags:
  - Fields
  properties:
  - type: OpenAPI
    url: openapi/zuva-fields-api-openapi.yml
  - type: Documentation
    url: https://zuva.ai/documentation/services/file-submission/
  - type: APIReference
    url: https://api-reference.zuva.ai/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/field-extraction-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/classification-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/services/language-classification/
  - type: Documentation
    url: https://zuva.ai/documentation/services/using-ocr/
  - type: Documentation
    url: https://zuva.ai/documentation/services/field-extraction/
- aid: zuva:zuva-files-api
  name: Zuva Files API
  description: Upload and manage document files.
  humanURL: https://zuva.ai/documentation/services/file-submission/
  baseURL: https://us.app.zuva.ai/api/v2
  tags:
  - File
  tags_raw:
  - Files
  properties:
  - type: OpenAPI
    url: openapi/zuva-files-api-openapi.yml
  - type: Documentation
    url: https://zuva.ai/documentation/services/file-submission/
  - type: APIReference
    url: https://api-reference.zuva.ai/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/field-extraction-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/classification-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/services/language-classification/
  - type: Documentation
    url: https://zuva.ai/documentation/services/using-ocr/
  - type: Documentation
    url: https://zuva.ai/documentation/services/field-extraction/
- aid: zuva:zuva-ocr-api
  name: Zuva OCR API
  description: Optical character recognition.
  humanURL: https://zuva.ai/documentation/services/file-submission/
  baseURL: https://us.app.zuva.ai/api/v2
  tags:
  - OCR
  properties:
  - type: OpenAPI
    url: openapi/zuva-ocr-api-openapi.yml
  - type: Documentation
    url: https://zuva.ai/documentation/services/file-submission/
  - type: APIReference
    url: https://api-reference.zuva.ai/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/field-extraction-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/workflows/classification-workflow/
  - type: Documentation
    url: https://zuva.ai/documentation/services/language-classification/
  - type: Documentation
    url: https://zuva.ai/documentation/services/using-ocr/
  - type: Documentation
    url: https://zuva.ai/documentation/services/field-extraction/
common:
- type: AgenticAccess
  url: agentic-access/zuva-agentic-access.yml
- type: DomainSecurity
  url: security/zuva-domain-security.yml
- type: Authentication
  url: authentication/zuva-authentication.yml
- type: GitHubOrganization
  url: https://github.com/zuvaai
- type: LinkedIn
  url: https://www.linkedin.com/company/zuva-inc
- type: Website
  url: https://zuva.ai/
- type: Documentation
  url: https://zuva.ai/documentation/
- type: Plans
  url: plans/zuva-plans-pricing.yml
- type: RateLimits
  url: rate-limits/zuva-rate-limits.yml
- type: FinOps
  url: finops/zuva-finops.yml
- url: https://zuva.ai/blog/
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Zuva API — frequently asked questions

Does Zuva have an API?

Yes. APIs.io lists 5 APIs from Zuva, including Zuva Classification API, Zuva Field Extraction API and Zuva Fields API, and 2 more.

Is there an OpenAPI specification for the Zuva API?

Yes. APIs.io indexes 5 OpenAPI specifications for Zuva, each linked for download from this page.

How do I authenticate with the Zuva API?

Zuva uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Zuva Authentication.

How much does the Zuva API cost?

APIs.io lists 3 pricing plans for Zuva, with each plan's price, limits and inclusions under Pricing on this page.

Is the Zuva API ready for AI agents?

Zuva has a Kin Score of 26.1 out of 100 (emerging) and an Agent Readiness score of 19.0 (agent-aware), scored by API Evangelist on 2026-11-13.

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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/zuva"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/zuva/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/zuva/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.