Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Security / Lakera API
Lakera API logo

Lakera API

67
AI ReadinessAI-Aware (B+)67/100
See full scorecard
Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer4 EndpointsREST

For Agents

Screen prompts and model output for prompt injection and unsafe content, read detailed detection results, and validate policy configuration with Lakera. Covers 4 endpoints across guard and policy operations.

Use for: Screen a user prompt for prompt injection before sending it to a model, Check a model's response for unsafe content before returning it, Get the detailed detection breakdown for a screened message, Validate a security policy configuration before rollout

Not supported: Does not host or run language models itself. Use for screening prompts and content against security policies only.

The Lakera API screens prompts and model output for security threats such as prompt injection, unsafe content, and data leakage, exposing guard and policy operations over a REST interface. It lets you send content to be screened, retrieve the detailed detection results, and validate a security policy configuration. Requests carry a bearer token and return structured JSON your application can act on before passing text to a model.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Lakera API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lakera API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flakera.ai%2Flakera" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flakera.ai%2Flakera" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lakera API.

Screen a prompt or model output for threats through the guard operation

Retrieve the detailed detection results for screened content

Check whether a security policy configuration is healthy

Validate a policy configuration before applying it

Use Cases

Patterns agents use Lakera API for, with concrete tasks.

★ AI Guardrail via Jentic

An AI agent can screen its own inputs and outputs through Lakera without a developer wiring the API by hand. Through Jentic the agent searches for the guard operation by intent, receives the Lakera endpoint and its input schema, and calls it with the bearer token injected at execution time. This lets a team add a screening step to an agent pipeline that runs directly against Lakera.

Search Jentic for 'screen content for threats', load the operation schema, and call POST /v2/guard on each prompt before it reaches the model

Prompt Injection Screening

Applications that pass user text to a language model need to catch prompt injection before it reaches the model. The Lakera API screens each message and flags injection attempts, so a gateway can block or sanitize the request. This keeps untrusted input from steering the model off its intended task.

Call POST /v2/guard with the incoming prompt and reject the request when the response flags an injection

Policy Configuration Validation

Security teams that manage screening policies need to confirm a configuration is valid before it goes live. The Lakera API lints a policy and reports its health, so a CI step can catch a broken configuration before deployment. This prevents a misconfigured policy from silently letting unsafe content through.

Call POST /v2/policies/lint on the candidate policy and POST /v2/policies/health to confirm it is valid before rollout

Key Endpoints

4 endpoints — the lakera api screens prompts and model output for security threats such as prompt injection, unsafe content, and data leakage, exposing guard and policy operations over a rest interface.

METHOD

PATH

DESCRIPTION

POST

/v2/guard

Screen content for threats

POST

/v2/guard/results

Get detailed detection results

POST

/v2/policies/health

Check policy configuration health

POST

/v2/policies/lint

Validate policy configuration

POST

/v2/guard

Screen content for threats

POST

/v2/guard/results

Get detailed detection results

POST

/v2/policies/health

Check policy configuration health

POST

/v2/policies/lint

Validate policy configuration

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

L

Lakera API

- AI-Aware (B+)
67/100
100
Foundational Compliance
59
Developer Experience & Jentic Compatibility
53
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
66
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

59

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

38%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

53

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4
66%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

44%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

66

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1
66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Lakera API by hand means setting the bearer token on every request and calling the guard and policy endpoints with the right request bodies yourself. Through Jentic you install once, import Lakera from the API Directory, store the token once, and your agent calls it.

Permission scoping

Lakera exposes four operations and no resource ids in the path, so scoping is by operation: you can allow content screening while withholding policy management. You choose which operations the agent may call, so a screening-only agent never touches policy configuration.

Credential isolation

Your Lakera token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'screen content for threats' or 'validate a policy', and Jentic returns the matching Lakera operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

OpenAI

→

Language models whose inputs and outputs Lakera screens

Screen prompts with Lakera before sending them to OpenAI models and screen the responses on the way back

Complementary

Anthropic

→

Language models whose inputs and outputs Lakera screens

Add a Lakera screening step around Anthropic Messages calls to catch prompt injection and unsafe content

Alternative

Hugging Face

→

Open models including content-moderation and safety classifiers

Choose a Hugging Face safety model when you want to self-run open classifiers instead of Lakera's hosted screening

FAQs

Specific to using Lakera API through Jentic.

What authentication does the Lakera API use?

The Lakera API authenticates with a bearer token in the Authorization header, as declared in its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context.

Can I screen prompts for injection with the Lakera API?

Yes. Call POST /v2/guard with the incoming prompt or model output, and the response flags threats such as prompt injection and unsafe content. Call POST /v2/guard/results when you need the detailed detection breakdown for a screened message.

What are the rate limits for the Lakera API?

The OpenAPI spec does not specify rate limits. Check the Lakera API documentation at https://docs.lakera.ai for current limits before screening high volumes of traffic.

How do I add Lakera screening to my agent through Jentic?

Search Jentic for 'screen content for threats', which resolves to the POST /v2/guard operation, and Jentic returns its input schema so your agent can call it on each prompt. Credentials are injected at call time from your own instance. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I restrict what my agent is allowed to do with the Lakera API?

Yes. Lakera exposes four operations with no resource ids in the path, so you scope by operation: allow content screening such as POST /v2/guard while withholding policy management like POST /v2/policies/lint, and every call the agent makes is logged by your own instance. You add operations to the allowed set only when you decide to.

Is there a Lakera MCP server?

You don't need an MCP server to give your agent Lakera. Jentic connects it directly from the API Directory: import Lakera, store your token once, and your agent calls the guard and policy operations on demand without loading another server's tool definitions into its context.

GET STARTED

Start building with Lakera API

Explore with Jentic One
View OpenAPI Document