Landing.ai
LandingAI, founded by Andrew Ng, builds production AI for visual and document understanding. Its flagship product is Agentic Document Extraction (ADE), which converts real-world documents — PDFs, images, Office files and spreadsheets — into structured, auditable data. ADE exposes a family of REST APIs: Parse (document to reading-order Markdown plus hierarchical blocks with per-block visual grounding), Extract (schema-driven field extraction with character-span grounding back into the source), Build Extract Schema, and the preview Classify, Section and Split APIs, each available synchronously or as asynchronous Jobs for large files. The current generation runs on the DPT-3 document pre-trained transformer. LandingAI also operates LandingLens, a computer-vision platform API for creating projects, uploading images, defining classes, training models and deploying them to LandingAI-hosted cloud endpoints, plus a Vision Tools API surfacing OWLv2, Florence-2, SAM2, CountGD, Depth Anything, PaddleOCR and other vision models as HTTP tools. The company ships official Python and TypeScript ADE libraries, a hosted remote MCP server, published Agent Skills, an llms.txt agent surface, US and EU data residency, and SOC 2 Type II, HIPAA and GDPR compliance with a zero data retention option.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Landing.ai the way a machine reads it — 20 machine-readable artifacts across 13 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 — Landing.ai scores 63.9/100 (strong), with a separate agent-readiness read of 62/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 Landing.ai
Each block below is one kind of artifact we hold for Landing.ai. 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 13
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.
Landing.ai Classes API
The Classes API from Landing.ai — 1 operation(s) for classes.
Landing.ai Deployment API
The Deployment API from Landing.ai — 2 operation(s) for deployment.
Landing.ai Extract API
The Extract API from Landing.ai — 3 operation(s) for extract.
Landing.ai Image API
The Image API from Landing.ai — 5 operation(s) for image.
Landing.ai Metadata API
The Metadata API from Landing.ai — 2 operation(s) for metadata.
Landing.ai Metrics API
The Metrics API from Landing.ai — 1 operation(s) for metrics.
Landing.ai Model API
The Model API from Landing.ai — 3 operation(s) for model.
Landing.ai Parse API
The Parse API from Landing.ai — 3 operation(s) for parse.
Landing.ai Project API
The Project API from Landing.ai — 3 operation(s) for project.
Landing.ai Snapshot API
The Snapshot API from Landing.ai — 3 operation(s) for snapshot.
Landing.ai Tags API
The Tags API from Landing.ai — 2 operation(s) for tags.
Landing.ai Tools API
The Tools API from Landing.ai — 50 operation(s) for tools.
Landing.ai Training API
The Training API from Landing.ai — 6 operation(s) for training.
Scroll within the panel for all 13 ·
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.
landingai-mcp.yml
MCP SERVERPricing 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.
Landingai Plans
PLANSRate 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.
Landingai Rate Limits
RATE LIMITSSecurity Posture 4
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 Landing.ai — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/landingai · machine-readable index on apis.io