Apache POI
Apache POI is a Java API for manipulating various file formats based upon the Office Open XML standards (OOXML) and Microsoft's OLE2 Compound Document format (OLE2). It supports reading and writing Excel, Word, PowerPoint, Visio, and Outlook files.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Apache POI the way a machine reads it — 76 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apache POI scores 48.2/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Apache POI
Each block below is one kind of artifact we hold for Apache POI. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache POI Conversion API
The Conversion API from Apache POI — 1 operation(s) for conversion.
Apache POI Excel API
The Excel API from Apache POI — 4 operation(s) for excel.
Apache POI PowerPoint API
The PowerPoint API from Apache POI — 2 operation(s) for powerpoint.
Apache POI Word API
The Word API from Apache POI — 2 operation(s) for word.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Poi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Poi Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Excel HSSF/XSSF
Read and write Excel files in legacy XLS (HSSF) and modern XLSX (XSSF) formats
Word HWPF/XWPF
Read and write Word documents in legacy DOC (HWPF) and modern DOCX (XWPF) formats
PowerPoint HSLF/XSLF
Create and manipulate PowerPoint presentations in PPT and PPTX formats
Formula Evaluation
Evaluate Excel formulas and compute cell values programmatically
Streaming API
Low-memory streaming API (SXSSF) for writing large Excel files
Chart Support
Create and modify charts in Excel workbooks and PowerPoint slides
Digital Signatures
Sign Office documents with digital signatures using OOXML standards
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apache Poi Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apache POI API Rules
SPECTRALApache POI API Rules
SPECTRALJSON Schema 16
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CellData
JSON SCHEMACell
JSON SCHEMAConversionRequest
JSON SCHEMAConversionResult
JSON SCHEMADocumentRequest
JSON SCHEMADocument
JSON SCHEMAParagraph
JSON SCHEMAPresentationRequest
JSON SCHEMAPresentation
JSON SCHEMAShape
JSON SCHEMASheetList
JSON SCHEMASheet
JSON SCHEMASlide
JSON SCHEMAWorkbookList
JSON SCHEMAWorkbookRequest
JSON SCHEMAWorkbook
JSON SCHEMAScroll within the panel for all 16 ·
JSON Structure 16
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Poi Cell Data Structure
JSON STRUCTUREApache Poi Cell Structure
JSON STRUCTUREApache Poi Conversion Request Structure
JSON STRUCTUREApache Poi Conversion Result Structure
JSON STRUCTUREApache Poi Document Request Structure
JSON STRUCTUREApache Poi Document Structure
JSON STRUCTUREApache Poi Paragraph Structure
JSON STRUCTUREApache Poi Presentation Request Structure
JSON STRUCTUREApache Poi Presentation Structure
JSON STRUCTUREApache Poi Shape Structure
JSON STRUCTUREApache Poi Sheet List Structure
JSON STRUCTUREApache Poi Sheet Structure
JSON STRUCTUREApache Poi Slide Structure
JSON STRUCTUREApache Poi Workbook List Structure
JSON STRUCTUREApache Poi Workbook Request Structure
JSON STRUCTUREApache Poi Workbook Structure
JSON STRUCTUREScroll within the panel for all 16 ·
Examples 16
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Apache Poi Cell Data Example
EXAMPLEApache Poi Cell Example
EXAMPLEApache Poi Document Example
EXAMPLEApache Poi Paragraph Example
EXAMPLEApache Poi Shape Example
EXAMPLEApache Poi Sheet Example
EXAMPLEApache Poi Slide Example
EXAMPLEApache Poi Workbook Example
EXAMPLEScroll within the panel for all 16 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Report Generation
Generate Excel and Word reports programmatically from application data
Data Import/Export
Import data from Excel spreadsheets and export results back
Template Processing
Fill Office document templates with dynamic data
Document Conversion
Convert between legacy Office formats and modern OOXML formats
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Tika
POI is used by Tika for Office document text extraction
Spring Framework
Integrate POI with Spring Boot for web-based document generation
Maven Central
Available as org.apache.poi artifacts on Maven Central
Apache Commons
Uses Commons Collections and Commons Math for data structures
Resources
Every other property we hold for Apache POI — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/apache-poi · machine-readable index on apis.io