Jentic publishes the only available OpenAPI specification for Customer.io API, keeping it validated and agent-ready. Customer.io is a marketing automation platform that combines behavioural messaging, segmentation, and transactional email into a single workflow tool. This API surface covers customer identification and lifecycle, event tracking, device management, segment and campaign listing, newsletter metrics, customer and delivery exports, and transactional email sending. Authentication uses HTTP Basic with a site ID and API key pair.
21 endpointsJentic publishes the only available OpenAPI specification for Customer.io Track API, keeping it validated and agent-ready. The Track API is the data ingestion surface for Customer.io, used to add and update people, record events, manage devices, suppress profiles, submit forms, merge duplicates, and send batched requests. It also includes account region discovery and a v2 entity endpoint for unified ingestion. Authentication uses HTTP Basic with a site ID and tracking API key.
16 endpointsJentic publishes the only available OpenAPI specification for Customer.io Track API, keeping it validated and agent-ready. This focused Track API surface covers customer identification and lifecycle, event tracking (attributed and anonymous), device registration, and suppression management. It is the minimal ingestion layer for sending behavioural data into Customer.io to drive messaging campaigns. Authentication uses HTTP Basic with a site ID and tracking API key.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.