Diligent

Diligent (Diligent AI, godiligent.ai) builds autonomous AI agents for financial-crime compliance, automating the reasoning-heavy KYC/AML workflows that banks and fintechs run at scale. Its API exposes Customer Due Diligence (CDD) and business/merchant verification, name screening against sanctions and PEP providers with AI-powered alert remediation, ongoing monitoring with alerting, company identification and registry document retrieval, a blocked-company list, and an experimental instant website screening endpoint. The platform is API-first (X-API-KEY auth, production and sandbox environments, idempotency, and signed webhooks) and is used by fintechs and banks including Scalapay, Flywire, Allica Bank, Tamara, Teya, Vivid and Alma. Diligent is SOC 2 Type II certified, ISO 27001 certified, and GDPR compliant. It is backed by Speedinvest, Y Combinator and Shapers, and operates out of London and Berlin.

Diligent publishes 6 API contracts indexed on the APIs.io network, including CDD API, Company API, Instant Screening (experimental) API, and 3 more. Tagged areas include Company, Compliance, RegTech, KYC, and AML.

The Diligent catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Diligent’s developer surface includes authentication, documentation, API reference, getting-started guide, support, engineering blog, sandbox, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.3/100 developing ▬ flat Agent 38/100 agent ready Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 4 Agent Skills

Company Compliance RegTech KYC AML Financial Crime Due Diligence Screening Sanctions Monitoring Artificial Intelligence Fintech Webhook

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Compliance Management

BC-130

CDDMonitoringsName Screening

POST /cdds GET /monitoring-alerts POST /monitorings POST /v1/name-screenings/alerts/remediate

Client Engagement Management

BC-4300

CDD

POST /cdds POST /cdds/{id}/run-checks

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 51.3/100 · developing

Contract Quality 10.5 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 6.5 / 15

Operational Transparency 1.5 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.1 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 38/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/diligent/"><img src="https://apis.io/badge/diligent/card.svg" alt="Diligent on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 43.4 — up to +11.3 composite points
Contract Quality scores 55.8 — up to +11.1 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/diligent/apis.yml: open an issue on github.com/api-evangelist/diligent to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Diligent CDD API

Customer Due Diligence

57 rules · 47 errors 7 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Diligent Api Overlay

1 action · update · diligent-openapi-original.json

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Diligent Authentication

apiKey · 1 scheme

SECURITY

Diligent Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Diligent Trust Center

SOC 2, ISO 27001, GDPR

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

DataModel

Webhooks

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Postman

Postman

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

Authentication

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Twitter

Twitter

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: diligent
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/diligent.png
name: Diligent
description: Diligent (Diligent AI, godiligent.ai) builds autonomous AI agents for financial-crime compliance, automating
  the reasoning-heavy KYC/AML workflows that banks and fintechs run at scale. Its API exposes Customer Due Diligence (CDD)
  and business/merchant verification, name screening against sanctions and PEP providers with AI-powered alert remediation,
  ongoing monitoring with alerting, company identification and registry document retrieval, a blocked-company list, and an
  experimental instant website screening endpoint. The platform is API-first (X-API-KEY auth, production and sandbox environments,
  idempotency, and signed webhooks) and is used by fintechs and banks including Scalapay, Flywire, Allica Bank, Tamara, Teya,
  Vivid and Alma. Diligent is SOC 2 Type II certified, ISO 27001 certified, and GDPR compliant. It is backed by Speedinvest,
  Y Combinator and Shapers, and operates out of London and Berlin.
url: https://raw.githubusercontent.com/api-evangelist/diligent/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- speedinvest
- ycombinator
x-tier: enriched
x-tier-reason: public-api-found
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-25
tags:
- Company
- Compliance
- RegTech
- KYC
- AML
- Financial Crime
- Due Diligence
- Screening
- Sanctions
- Monitoring
- Artificial Intelligence
- Fintech
- Webhook
tags_raw:
- Company
- Compliance
- RegTech
- KYC
- AML
- Financial Crime
- Due Diligence
- Screening
- Sanctions
- Monitoring
- Artificial Intelligence
- Fintech
- Webhooks
apis:
- aid: diligent:diligent-cdd-api
  name: Diligent CDD API
  description: Customer Due Diligence
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - CDD
  properties:
  - type: OpenAPI
    url: openapi/diligent-cdd-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
- aid: diligent:diligent-company-api
  name: Diligent Company API
  description: Company Information
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - Company
  properties:
  - type: OpenAPI
    url: openapi/diligent-company-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
- aid: diligent:diligent-instant-screening-experimental-api
  name: Diligent Instant Screening (experimental) API
  description: Instant Website Screening API
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - Instant Screening (experimental)
  properties:
  - type: OpenAPI
    url: openapi/diligent-instant-screening-experimental-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
- aid: diligent:diligent-monitorings-api
  name: Diligent Monitorings API
  description: Website monitoring and alerts for changes and risks
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - Monitorings
  properties:
  - type: OpenAPI
    url: openapi/diligent-monitorings-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
- aid: diligent:diligent-name-screening-api
  name: Diligent Name Screening API
  description: Name screening remediation
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - Name Screening
  properties:
  - type: OpenAPI
    url: openapi/diligent-name-screening-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
- aid: diligent:diligent-webhooks-api
  name: Diligent Webhooks API
  description: "## How to Secure Webhook Deliveries\nTo ensure that webhook payloads are securely transmitted and verified.\
    \ This guide explains how to configure and validate\nwebhook deliveries using a shared secret.\n\n### How It Works\n\n\
    When setting up a webhook, a secret is configured on both the sender (our system) and the receiver (your endpoint). Each\n\
    webhook payload is signed using this secret, allowing the receiver to verify its authenticity.\n\n#### Step 1: Configuring\
    \ Your Webhook Secret\n\n1. When creating a webhook in our system, specify a unique secret key. This secret should be\
    \ a strong, randomly\ngenerated string.\n2. Store this secret securely on your server; it should never be exposed publicly.\n\
    \n#### Step 2: Receiving Webhook Payloads\n\nWhen your server receives a webhook event, the request will include an `X-Signature`\
    \ header containing a HMAC signature\nof the payload.\n\nExample header:\n\n```\nX-Signature: sha256=abcdef1234567890...\n\
    ```\n\n#### Step 3: Validating the Webhook Signature\n\nTo verify the webhook payload:\n\n1. Retrieve the `X-Signature`\
    \ value from the request headers.\n2. Compute the HMAC SHA-256 signature of the request payload using your webhook secret.\n\
    3. Compare the computed signature with the one in the `X-Signature` header.\n4. If they match, the webhook is valid.\n\
    \n#### (Python)\n\n```python\nimport hashlib\nimport hmac\nimport json\n\ndef verify_webhook_signature(secret, payload,\
    \ signature):\n  computed_signature = hmac.new(secret.encode(), payload.encode(), hashlib.sha256).hexdigest()\n  expected_signature\
    \ = f\"sha256={computed_signature}\"\n  return hmac.compare_digest(expected_signature, signature)\n\n# Example usage:\n\
    secret = \"your_webhook_secret\"\npayload = json.dumps({\"event\": \"example\"})\nreceived_signature = \"sha256=abcdef1234567890...\"\
    \n\nif verify_webhook_signature(secret, payload, received_signature):\n  print(\"Valid webhook received!\")\nelse:\n \
    \ print(\"Invalid webhook signature!\")\n```\n\n#### (JavaScript)\n\n```javascript\nconst crypto = require('crypto');\n\
    \nfunction verifyWebhookSignature (secret, payload, signature) {\nconst computedSignature = `sha256=${crypto.createHmac('sha256',\
    \ secret)\n.update(payload)\n.digest('hex')}`;\nreturn crypto.timingSafeEqual(Buffer.from(computedSignature), Buffer.from(signature));\n\
    }\n\n// Example usage:\nconst secret = \"your_webhook_secret\";\nconst payload = JSON.stringify({ event: \"example\" });\n\
    const receivedSignature = \"sha256=abcdef1234567890...\";\n\nif (verifyWebhookSignature(secret, payload, receivedSignature))\
    \ {\nconsole.log(\"Valid webhook received!\");\n} else {\nconsole.log(\"Invalid webhook signature!\");\n}\n```\n\n####\
    \ Security Considerations\n\n- Always use HTTPS to prevent interception of webhook payloads.\n- Reject webhook requests\
    \ that fail signature validation.\n- Rotate secrets periodically to enhance security.\n\nBy following this guide, you\
    \ ensure that webhook deliveries are secure and trusted."
  humanURL: https://docs.godiligent.ai/guides/introduction
  baseURL: https://api.godiligent.ai
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/diligent-webhooks-api-openapi.yml
  - type: Documentation
    url: https://docs.godiligent.ai/guides/introduction
  - type: APIReference
    url: https://docs.godiligent.ai/guides/introduction
  - type: GettingStarted
    url: https://docs.godiligent.ai/guides/introduction
  - type: Documentation
    url: https://docs.godiligent.ai/guides/name-screening/remediation-api
common:
- type: CapabilityMap
  url: capabilities/diligent-capability-edges.yml
  name: Diligent Business Capability Map
- type: Overlay
  url: overlays/diligent-api-overlay.yaml
- type: TrustCenter
  url: security/diligent-trust-center.yml
- type: DomainSecurity
  url: security/diligent-domain-security.yml
- type: Authentication
  url: authentication/diligent-authentication.yml
- type: Website
  url: https://www.godiligent.ai
- type: DeveloperPortal
  url: https://docs.godiligent.ai
- type: Documentation
  url: https://docs.godiligent.ai
- type: APIReference
  url: https://docs.godiligent.ai/guides/introduction
- type: GettingStarted
  url: https://docs.godiligent.ai/guides/introduction
- type: Login
  url: https://app.godiligent.ai/
- type: Support
  url: https://docs.godiligent.ai/support
- type: Blog
  url: https://www.godiligent.ai/news
- type: TermsOfService
  url: https://www.godiligent.ai/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.godiligent.ai/privacy-policy
- type: StatusPage
  url: https://status.godiligent.ai/
- type: Compliance
  url: https://www.godiligent.ai/security
- type: LinkedIn
  url: https://www.linkedin.com/company/godiligentai
- type: Twitter
  url: https://x.com/goDiligent
- type: Postman
  url: https://raw.githubusercontent.com/paylaneio/api/refs/heads/master/postman_collection.json
- type: LLMsTxt
  url: llms/diligent-llms.txt
- type: X-MCPServerCandidate
  url: mcp/diligent-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  name: Diligent MCP (candidate)
  description: Candidate MCP tool list derived from the Diligent OpenAPI operations; no official hosted server published.
- type: Conformance
  url: conformance/diligent-conformance.yml
- type: ErrorCatalog
  url: errors/diligent-problem-types.yml
- type: Lifecycle
  url: lifecycle/diligent-lifecycle.yml
- type: Conventions
  url: conventions/diligent-conventions.yml
- type: Idempotency
  url: conventions/diligent-conventions.yml
- type: DataModel
  url: data-model/diligent-data-model.yml
- type: Sandbox
  url: sandbox/diligent-sandbox.yml
- type: Webhooks
  url: asyncapi/diligent-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Diligent API — frequently asked questions

Does Diligent have an API?

Yes. APIs.io lists 6 APIs from Diligent, including Diligent CDD API, Diligent Company API and Diligent Instant Screening (experimental) API, and 3 more.

Is there an OpenAPI specification for the Diligent API?

Yes. APIs.io indexes 6 OpenAPI specifications for Diligent, each linked for download from this page.

How do I authenticate with the Diligent API?

Diligent uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Diligent Authentication.

Is the Diligent API ready for AI agents?

Diligent has a Kin Score of 51.3 out of 100 (developing) and an Agent Readiness score of 37.9 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/diligent"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/diligent/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/diligent/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.