Lakera
Lakera is an AI security company building runtime defenses for generative AI applications. Its flagship Lakera Guard API screens prompts and responses for prompt injection, jailbreaks, PII leakage, unsafe content, and policy violations, while Lakera Red provides automated red teaming and risk assessment for GenAI systems. Lakera follows an API-first architecture with a managed SaaS platform, regional endpoints, self-hosted deployments for regulated environments, and a free Gandalf training game that has driven much of the prompt injection research community.
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 Lakera the way a machine reads it — 34 machine-readable artifacts across 6 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 — Lakera scores 47.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Lakera
Each block below is one kind of artifact we hold for Lakera. 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 6
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.
Lakera Guard
Lakera Guard is a low-latency screening API that inspects text content sent to or from LLMs and flags threats including prompt injection, jailbreaks, PII, profanity, and policy ...
Lakera Red
Lakera Red is an automated red teaming product that probes GenAI applications for jailbreaks, prompt injection, data leakage, and other adversarial failures, then produces a ris...
Gandalf
Gandalf is Lakera's free interactive game that teaches prompt injection by challenging players to extract a secret from an LLM across progressively harder defenses. It has becom...
Lakera Guard API
Screen prompts and model responses for threats
Lakera Health API
Kubernetes-style health and lifecycle probes (self-hosted)
Lakera Policies API
Policy validation (self-hosted)
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Lakera Guard API
OPEN COLLECTIONPricing 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.
Lakera Plans Pricing
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.
Lakera 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.
Lakera Finops
FINOPSFeatures 8
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.
Prompt Injection Detection
Detects direct and indirect prompt injection attempts targeting LLM-powered applications and agents.
Jailbreak Detection
Identifies attempts to bypass system prompts, safety policies, and model guardrails.
PII Detection
Screens prompts and responses for personally identifiable information leakage.
Content Moderation
Flags unsafe, toxic, or policy-violating content in user inputs and model outputs.
Custom Policies
Configurable detection policies scoped to projects, models, and use cases.
Regional Endpoints
Hosted endpoints in US, EU, and APAC regions for data residency and latency.
Self-Hosted Deployment
On-premises and VPC deployments for regulated industries that cannot send data to a SaaS.
MCP Server
Model Context Protocol server for embedding Lakera Guard into AI clients like Claude Code and Cursor.
Scroll within the panel for all 8 ·
Security 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.
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 5
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.
LLM Application Guardrails
Screen inputs and outputs of chatbots, copilots, and RAG applications for prompt injection and unsafe content.
AI Agent Protection
Inspect tool inputs, retrieved context, and agent reasoning steps for indirect prompt injection.
Workforce AI Security
Govern employee use of public LLMs and prevent sensitive data exfiltration.
GenAI Red Teaming
Run automated adversarial assessments against pre-production GenAI applications.
Regulated Industry Deployments
Self-host Guard in financial services, healthcare, and government environments with strict data residency.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
OpenAI
Wrap OpenAI calls with Guard screening for input and output safety.
Anthropic
Screen prompts and responses from Anthropic Claude models.
LangChain
Drop-in callbacks and chains for integrating Guard into LangChain applications.
LlamaIndex
Screen queries and retrieved context in LlamaIndex RAG pipelines.
Model Context Protocol
MCP server for surfacing Lakera Guard inside Claude Code, Cursor, and other MCP clients.
Kubernetes
Self-hosted Helm-based deployments with health, readiness, and liveness probes.
Resources
Every other property we hold for Lakera — 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 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lakera · machine-readable index on apis.io