API and MCP

Everything Cloudpliant screens is also available programmatically: per register or as a full frozen report. Through the REST API for your own software, or through MCP for AI assistants.

REST API

Create an API key in the dashboard under Settings and send it as the x-api-key header. The full reference with every endpoint and schema is at ai.cloudpliant.com/v1/docs.

curl -X POST https://ai.cloudpliant.com/v1/person/sanctions \
  -H "x-api-key: YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"first_name": "Jan", "last_name": "Jansen", "country": "NL"}'

Besides single checks (sanctions, PEP, insolvency), POST /v1/person/report or /v1/organization/report generates a full report: all checks, risk classification and shareable report URLs (html, pdf, json).

MCP for AI assistants

The same capability is available as a Model Context Protocol server at https://ai.cloudpliant.com/v1/mcp (Streamable HTTP, stateless). Authenticate with the same x-api-key header. Tools: screen_person, screen_organization, check_person, check_organization and api_status. Why this is safe to do is covered on the AI page.

claude mcp add cloudpliant https://ai.cloudpliant.com/v1/mcp \
  --transport http --header "x-api-key: YOUR_KEY"

Versioning and limits

The /v1 wire format is stable: existing fields are never renamed or removed, new fields may be added. Screenings incur costs at the source registers; identical requests within 24 hours are served from cache and do not count. A daily screening quota applies per team.

No account yet? Create one and generate your key under Settings.