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.

The DinMo catalog on APIs.io includes 1 event-driven AsyncAPI specification.

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

🌐 Visit website 📡 Source on GitHub

55.4/100 strong ▬ flat Agent 25/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessPaidFree trial

1 APIs

Company Customer Data Platform CDP Reverse ETL Data Activation Data Warehouse Audience Segmentation Marketing Personalization MarTech

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 55.4/100 · strong

Contract Quality 8.3 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 14.3 / 17

Operational Transparency 4.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 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

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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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

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 github.com/api-evangelist/dinmo: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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

Pricing Plans 1

Published pricing tiers and plan structures.

Dinmo Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Dinmo Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

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

Dinmo Webhooks

ASYNCAPI

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

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Webhooks

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Compliance

Compliance

Learn 2

Tutorials, courses, talks, and written guidance

Tutorials

Tutorials

YouTube

YouTube

Operate 4

Status, limits, changes, and where to get help

Support

ChangeLog

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 1

Properties that don't map to a standard resource type

CaseStudies

CaseStudies

Source (apis.yml)

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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  pricing_from: 350 EUR / month (Starter); a 250 EUR / month startup plan is available on qualification
  onboarding: sales-assisted
  trial: true
  trial_terms: 30-day free trial advertised on the pricing page
  try_now: false
  public: false
  label: Paid plans from 350 EUR/month, annual commitment, 30-day trial
  confidence: high
  source:
  - https://www.dinmo.com/pricing
  - plans/dinmo-plans-pricing.yml
  - https://docs.dinmo.io/customer-hub/profiles-api.md
  note: Plans are published with prices, but the Personalization API must be enabled for a workspace by DinMo before it can
    be used, so programmatic access is sales-gated rather than self-serve.
  generated: '2026-08-13'
  method: searched
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
image: https://www.dinmo.com/favicon.ico
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-25
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: X-MCPServerCandidate
    url: mcp/dinmo-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.'
  - type: RateLimits
    url: rate-limits/dinmo-rate-limits.yml
  - type: DataModel
    url: data-model/dinmo-data-model.yml
  - type: Lifecycle
    url: lifecycle/dinmo-lifecycle.yml
  - type: GettingStarted
    url: https://docs.dinmo.io/customer-hub/profiles-api/set-up
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: X-MCPServerCandidate
  url: mcp/dinmo-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.'
- type: Plans
  url: plans/dinmo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/dinmo-rate-limits.yml
- type: Conformance
  url: conformance/dinmo-conformance.yml
- type: Compliance
  url: conformance/dinmo-conformance.yml
  name: SOC 2 Type 2, GDPR, CCPA (published in DinMo security and privacy docs)
- type: DataModel
  url: data-model/dinmo-data-model.yml
- type: Webhooks
  url: asyncapi/dinmo-webhooks.yml
  name: Webhook destination connector (DinMo is the sender; no AsyncAPI published)
- type: Integrations
  url: https://www.dinmo.com/integrations/
- type: Tutorials
  url: https://www.dinmo.com/tutorials/
- type: CaseStudies
  url: https://www.dinmo.com/customer-stories/
- type: LinkedIn
  url: https://www.linkedin.com/company/dinmo-io/
- type: YouTube
  url: https://www.youtube.com/@DinMoTube
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 6
  pass: local-v1

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/dinmo"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.