canonical: https://jentic.com/apis/interpol.int/interpol

# Interpol Int Interpol Red Notice API

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.

## For AI 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.

## Scope

Does not issue notices, verify identities, or run background checks. Use for querying public Interpol Red and Yellow Notices only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Yellow Notices for a name and report any matching missing-person notices

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/notices/v1/red` | Search and list Red Notices |
| GET | `/notices/v1/red/{entityId}` | Get a specific Red Notice by entity id |
| GET | `/notices/v1/red/{entityId}/images` | Get images associated with a Red Notice |
| GET | `/notices/v1/yellow` | Search and list Yellow Notices |

## Key resources

- **Red Notices** — Search Red Notices, retrieve one by entity id, and fetch its images
- **Yellow Notices** — Search and list Yellow Notices for missing persons
- **Images** — Retrieve the images associated with a Red Notice

## AI readiness

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.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 81 / 100
- **View full report:** https://jentic.com/apis/interpol.int/interpol/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

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

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **OpenSanctions API** — OpenSanctions screens against sanctions and watchlists, a broader screening dataset than Interpol's public notices.
- **ComplyAdvantage API** — ComplyAdvantage runs AML and sanctions screening with adverse-media coverage, where Interpol exposes only its public notices.
- **Onfido Public API** — Onfido verifies identity documents, complementing a notice check with proof the person is who they claim.

## FAQ

### 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.