Customer Database
Customer Database is the topic dedicated to APIs, schemas, vocabularies, and reference designs for the systems of record that store customer identity, profile, contact, preference, consent, and account data. A customer database underpins CRM, marketing automation, customer data platforms (CDPs), customer service, billing, and analytics use cases, and is increasingly expected to support API-first access, schema-on-write data quality, real-time eventing, GDPR/CCPA consent and erasure workflows, and identity resolution across web, mobile, and offline channels. This repository tracks the vendors, standards, and patterns that make customer data accessible, governed, and portable.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Customer Database the way a machine reads it — 11 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Customer Database scores 13.9/100 (emerging), with a separate agent-readiness read of 2/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Customer Database is an API Evangelist topic reference, not a company — apis.yml declares apis: [] and the profile exists to point at the vendors and open standards in the customer-data space, so there is no vendor, no host, and no API of its own to document. repair-api-bases.py returned "missing" and probe-domain-security.py returned "no-hosts" because no API entry names a base URL. The 14 artifacts added this pass are neutral, standards-grounded reference material (a vocabulary, a SCIM/vCard/Schema.org field crosswalk, five JSON Schemas, a JSON Structure, a JSON-LD context, a Spectral ruleset, examples and an llms.txt), not a vendor surface. See the individual vendor repositories — salesforce, hubspot, segment, customer-io, zendesk — for real APIs.
This is an honest zero, not a gap in our research. Customer Database does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://raw.githubusercontent.com/api-evangelist/customer-database/refs/heads/main/apis.yml→ HTTP 200https://schema.org/version/latest/schemaorg-current-https.jsonld→ HTTP 200https://www.rfc-editor.org/rfc/rfc7643.txt→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Customer Database's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/customer-database/"
title="Customer Database on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/customer-database.svg"
alt="Customer Database Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/customer-database/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/customer-database/"
title="Customer Database on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/customer-database/card.svg"
alt="Customer Database Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Customer Database
Each block below is one kind of artifact we hold for Customer Database. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Customer Database Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Customer Database API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Customer Consent Record
JSON SCHEMACustomer Contact Point
JSON SCHEMACustomer Identity Link
JSON SCHEMACustomer Postal Address
JSON SCHEMACustomer Record
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Customer Database Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Customer Record Example
EXAMPLEResources
Every other property we hold for Customer Database — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/customer-database · machine-readable index on apis.io
This is an independent, third-party profile of Customer Database, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.