Lilt
LILT is an AI translation and localization platform that pairs contextual, adaptive machine translation with human linguist verification. The LILT REST API (https://api.lilt.com) exposes the platform programmatically: adaptive machine translation, large-scale translation memory and the Lexicon termbase, document and file translation, job/project/segment management, Lilt Create multilingual content generation, workflow templates, domains, cloud and multipart uploads, and webhook configuration. LILT also ships connectors for CMS, DAM and repository systems, first-party Python, Node and Java SDKs, and a hosted remote MCP server at mcp.lilt.com for agent-driven translation.
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 Lilt the way a machine reads it — 21 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 — Lilt scores 59.7/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 Lilt
Each block below is one kind of artifact we hold for Lilt. 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.
Lilt Create API
The Create API from Lilt — 2 operation(s) for create.
Lilt Documents API
The Documents API from Lilt — 2 operation(s) for documents.
Lilt Domains API
The Domains API from Lilt — 1 operation(s) for domains.
Lilt Files API
The Files API from Lilt — 3 operation(s) for files.
Lilt Jobs API
The Jobs API from Lilt — 9 operation(s) for jobs.
Lilt Languages API
The Languages API from Lilt — 1 operation(s) for languages.
Lilt Memories API
The Memories API from Lilt — 6 operation(s) for memories.
Lilt Projects API
The Projects API from Lilt — 1 operation(s) for projects.
Lilt Segments API
The Segments API from Lilt — 3 operation(s) for segments.
Lilt Translate API
The Translate API from Lilt — 3 operation(s) for translate.
Lilt Uploads API
The Uploads API from Lilt — 7 operation(s) for uploads.
Lilt Webhook Configuration API
The Webhook Configuration API from Lilt — 2 operation(s) for webhook configuration.
Lilt Workflows API
The Workflows API from Lilt — 1 operation(s) for workflows.
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.
lilt-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.
Lilt 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.
Lilt Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Lilt — 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 3
Portal, sign-up, and the first successful call
Documentation 3
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 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
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/lilt · machine-readable index on apis.io