Qomplement
Qomplement is a San Francisco-based Y Combinator (Spring 2026) company building an AI-native platform for supply chain and document-heavy back-office operations. Its publicly documented developer product is the Qomplement StructDatafy API, a REST API that extracts structured data from documents in 30+ formats, fills PDF forms, and populates Excel templates programmatically using AI OCR and structuring models. The API is asynchronous (job-based), authenticated with Bearer API keys issued from the developer portal, rate limited per minute and per month, and ships first-party Python and Node.js SDKs. This profile captures the published API surface, SDKs, authentication, conventions, error model, webhooks, and lifecycle.
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 Qomplement the way a machine reads it — 12 machine-readable artifacts across 7 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 — Qomplement scores 50.2/100 (developing), with a separate agent-readiness read of 67/100 (agent native). 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 Qomplement
Each block below is one kind of artifact we hold for Qomplement. 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 7
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.
Qomplement API Keys API
The API Keys API from Qomplement — 2 operation(s) for api keys.
Qomplement Extract API
The Extract API from Qomplement — 3 operation(s) for extract.
Qomplement Fill Excel API
The Fill Excel API from Qomplement — 1 operation(s) for fill excel.
Qomplement Fill PDF API
The Fill PDF API from Qomplement — 1 operation(s) for fill pdf.
Qomplement Health API
The Health API from Qomplement — 2 operation(s) for health.
Qomplement Jobs API
The Jobs API from Qomplement — 3 operation(s) for jobs.
Qomplement Usage API
The Usage API from Qomplement — 1 operation(s) for usage.
Scroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
qomplement-mcp.yml
MCP SERVERRate 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.
Qomplement Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Qomplement Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for Qomplement — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/qomplement · machine-readable index on apis.io