Diligent website screenshot

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

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

54.7/100 developing ▬ flat Agent 65/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
6 APIs 1 MCP Servers
CompanyComplianceRegTechKYCAMLFinancial CrimeDue DiligenceScreeningSanctionsMonitoringArtificial IntelligenceFintechWebhooks

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 54.7/100 · developing
Contract Quality 15.9 / 25
Developer Ergonomics 15.7 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 3.1 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 65/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/diligent: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 6

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

Diligent CDD API

Customer Due Diligence

Diligent Company API

Company Information

Diligent Instant Screening (experimental) API

Instant Website Screening API

Diligent Monitorings API

Website monitoring and alerts for changes and risks

Diligent Name Screening API

Name screening remediation

Diligent Webhooks API

## How to Secure Webhook Deliveries To ensure that webhook payloads are securely transmitted and verified. This guide explains how to configure and validate webhook deliveries u...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Diligent MCP (candidate)

Candidate MCP tool list derived from the Diligent OpenAPI operations; no official hosted server published.

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: diligent
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- 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:
  - 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: 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: MCPServer
  url: mcp/diligent-mcp.yml
  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