DinMo website screenshot

DinMo

DinMo is a composable Customer Data Platform (CDP) that turns a cloud data warehouse into a marketing activation engine. It connects directly to Snowflake, Google BigQuery, Databricks, Amazon Redshift, PostgreSQL, Microsoft Fabric, and ClickHouse, lets non-technical teams model customer data and build no-code segments, and activates those audiences to more than a hundred destination platforms (ad networks, CRMs, marketing and messaging tools) via Reverse ETL with a zero-data-copy architecture built for GDPR and FADP compliance. DinMo also exposes a Personalization API for retrieving activated model records in real time, plus AI predictions (LTV, churn), identity resolution, a Customer Hub, and event tracking. The company is Paris-based and backed by Seedcamp.

DinMo publishes 1 API on the APIs.io network. Tagged areas include Company, Customer Data Platform, CDP, Reverse ETL, and Data Activation.

DinMo’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, changelog, pricing, and 13 more developer resources.

32.4/100 thin ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs 1 MCP Servers
CompanyCustomer Data PlatformCDPReverse ETLData ActivationData WarehouseAudience SegmentationMarketingPersonalizationMarTech

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 32.4/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 12.2 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 29/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 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/dinmo: 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 1

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

DinMo Personalization API

Real-time read API for retrieving an activated model record (customer profile and its mapped activation attributes) by lookup key, for personalization use cases in apps and webs...

MCP Servers 1

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

dinmo-mcp.yml

MCP SERVER

Security Posture 2

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

Dinmo Authentication

http · 1 scheme

SECURITY

Dinmo Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: dinmo
name: DinMo
description: DinMo is a composable Customer Data Platform (CDP) that turns a cloud data warehouse into a marketing activation
  engine. It connects directly to Snowflake, Google BigQuery, Databricks, Amazon Redshift, PostgreSQL, Microsoft Fabric, and
  ClickHouse, lets non-technical teams model customer data and build no-code segments, and activates those audiences to more
  than a hundred destination platforms (ad networks, CRMs, marketing and messaging tools) via Reverse ETL with a zero-data-copy
  architecture built for GDPR and FADP compliance. DinMo also exposes a Personalization API for retrieving activated model
  records in real time, plus AI predictions (LTV, churn), identity resolution, a Customer Hub, and event tracking. The company
  is Paris-based and backed by Seedcamp.
url: https://raw.githubusercontent.com/api-evangelist/dinmo/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: stub
x-tier-reason: portfolio-lead
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
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-18'
image: https://www.dinmo.com/favicon.ico
tags:
- Company
- Customer Data Platform
- CDP
- Reverse ETL
- Data Activation
- Data Warehouse
- Audience Segmentation
- Marketing
- Personalization
- MarTech
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: DinMo Personalization API
  description: Real-time read API for retrieving an activated model record (customer profile and its mapped activation attributes)
    by lookup key, for personalization use cases in apps and websites. Authenticated with a Personalization API key sent as
    a Bearer token.
  humanURL: https://docs.dinmo.io/customer-hub/profiles-api/api-reference
  baseURL: https://data-export-api.dinmo.io/v1
  tags:
  - Personalization
  - Customer Data Platform
  - Profiles
  properties:
  - type: APIReference
    url: https://docs.dinmo.io/customer-hub/profiles-api/api-reference
  - type: Authentication
    url: authentication/dinmo-authentication.yml
  - type: ErrorCatalog
    url: errors/dinmo-problem-types.yml
  - type: Conventions
    url: conventions/dinmo-conventions.yml
  - type: MCPServer
    url: mcp/dinmo-mcp.yml
common:
- type: Website
  url: https://www.dinmo.com
- type: DeveloperPortal
  url: https://docs.dinmo.io
- type: Documentation
  url: https://docs.dinmo.io
- type: APIReference
  url: https://docs.dinmo.io/customer-hub/profiles-api/api-reference
- type: GettingStarted
  url: https://docs.dinmo.io/guides/get-started-with-dinmo
- type: Support
  url: https://www.dinmo.com/contact/
- type: Blog
  url: https://www.dinmo.com/blog/
- type: ChangeLog
  url: https://news.dinmo.com/
- type: Pricing
  url: https://www.dinmo.com/pricing
- type: SignUp
  url: https://app.dinmo.io/sign-in
- type: TermsOfService
  url: https://www.dinmo.com/terms-of-service/
- type: PrivacyPolicy
  url: https://www.dinmo.com/legals/privacy/
- type: LLMsTxt
  url: llms/dinmo-llms.txt
- type: Authentication
  url: authentication/dinmo-authentication.yml
- type: ErrorCatalog
  url: errors/dinmo-problem-types.yml
- type: Conventions
  url: conventions/dinmo-conventions.yml
- type: Lifecycle
  url: lifecycle/dinmo-lifecycle.yml
- type: ChangeLog
  url: changelog/dinmo-changelog.yml
  name: DinMo Changelog (structured)
- type: DomainSecurity
  url: security/dinmo-domain-security.yml
- type: MCPServer
  url: mcp/dinmo-mcp.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence