Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interpol Red Notice 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.
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%2Finterpol.int%2Finterpol" | shStep 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%2Finterpol.int%2Finterpol" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Interpol Red Notice API.
Search and list Red Notices for wanted individuals
Retrieve a specific Red Notice by its entity id
Fetch the images associated with a Red Notice
Search and list Yellow Notices for missing persons
Patterns agents use Interpol Red Notice API for, with concrete tasks.
GET STARTED
★ Agent-Driven Notice Screening
An AI agent connected through Jentic screens a person against Interpol's public notices by searching Red Notices for a name and nationality and reading any matching notice's details. Because the search is a single public call, the agent runs the check during onboarding or due diligence without a human querying the Interpol site by hand.
Search Red Notices for a given name and nationality and report any matching entity id and details
Notice Detail and Image Lookup
Investigation tools pull a specific notice and its images. The Interpol API returns a Red Notice by entity id and a separate images operation returns the pictures tied to it, so an agent assembles the full public record for a matched individual.
Retrieve a Red Notice by entity id and fetch its associated images for a case record
Missing Persons Search
Teams tracing a missing person search the Yellow Notices. The Interpol API lists Yellow Notices, which concern missing and unidentified persons, so an agent checks the public missing-persons notices alongside the wanted-persons Red Notices.
Search Yellow Notices for a name and report any matching missing-person notices
4 endpoints — the interpol red notice api searches and retrieves interpol's public red and yellow notices.
METHOD
PATH
DESCRIPTION
/notices/v1/red
Search and list Red Notices
/notices/v1/red/{entityId}
Get a specific Red Notice by entity id
/notices/v1/red/{entityId}/images
Get images associated with a Red Notice
/notices/v1/yellow
Search and list Yellow Notices
/notices/v1/red
Search and list Red Notices
/notices/v1/red/{entityId}
Get a specific Red Notice by entity id
/notices/v1/red/{entityId}/images
Get images associated with a Red Notice
/notices/v1/yellow
Search and list Yellow Notices
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Interpol Red Notice API by hand means building the notice search queries and paging the results yourself; it is public, so there is no auth to configure. Through Jentic you install once, import it from the API Directory, and your agent calls the Red and Yellow Notice operations.
Permission scoping
Every Interpol Red Notice operation is a read lookup over public notices, so there is nothing destructive to guard against. You still choose which your agent may call, so a rule can allow searching and reading Red Notices while leaving Yellow Notice search out unless you add it.
Credential isolation
The Interpol Red Notice API is public and needs no credential, so there is nothing to store. Your agent still calls it through your own Jentic One instance, keeping the request on your own infrastructure.
Intent-based discovery
Agents search Jentic by intent such as 'search Interpol Red Notices' or 'get a notice by entity id', and Jentic returns the matching Interpol operation with its query parameters so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Interpol Red Notice API through Jentic.
What authentication does the Interpol Red Notice API use?
The Interpol Red Notice API is a public web service and requires no authentication per its OpenAPI spec; its notice operations are open. Through Jentic the call still runs from your own Jentic One instance, so even an unauthenticated request stays on your own infrastructure.
Can I search Interpol Red Notices by name with the Interpol Red Notice API?
Yes. The Red Notice search operation lists notices matching your query, and you then retrieve a specific notice by its entity id and fetch its images. Your agent screens a name and assembles the public record for any match.
What are the rate limits for the Interpol Red Notice API?
The OpenAPI spec does not specify rate limits for the public web service. Check the Interpol public notices site at https://www.interpol.int/How-we-work/Notices for current usage guidance before running bulk screening jobs.
Is there an Interpol MCP server?
You do not need an MCP server to give your agent the Interpol Red Notice API. Jentic connects it directly from the API Directory: import it, and your agent calls the Red and Yellow Notice operations on demand without loading an extra server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Interpol Red Notice API?
Yes. Every operation is a read lookup over public notices, so write a rule that allows only the Red Notice search and detail operations and the agent can look up Red Notices and their images while leaving Yellow Notice search out unless you add it. You choose which operations it may call, and every call it makes is logged.
How do I screen a person against Interpol notices through Jentic?
Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Interpol Red Notice API from the Jentic directory and search by intent such as 'search Interpol Red Notices'. Jentic returns the matching operation with its query parameters so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Search Interpol's public Red and Yellow Notices, retrieve a specific Red Notice by entity id, and fetch its associated images, for screening a person against international notice records.
Use for: Search Interpol Red Notices for a given name, Get the details of a Red Notice by its entity id, Fetch the images associated with a Red Notice, Search Yellow Notices for a missing person
Not supported: Does not issue notices, verify identities, or run background checks. Use for querying public Interpol Red and Yellow Notices only.
The Interpol Red Notice API searches and retrieves Interpol's public Red and Yellow Notices. Red Notices identify individuals wanted by member countries, and the API returns a notice's personal details and the images associated with it when queried by entity id. A separate operation searches Yellow Notices, which concern missing persons, so a workflow can screen a name against both public notice types.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>