How to Connect Customer.io to an AI Agent
Auth setup
1. Go to customer.io > Settings > API Credentials. 2. Track API: use site_id and API key. 3. App API: create Bearer token for campaigns/segments.
Key facts
| Base URL | https://track.customer.io/api/v1/ |
|---|
| API version | v1 (Track) + v1 (App) |
|---|
| Auth | Track API: site_id:api_key as Basic auth. App API: Bearer token from app.customer.io. |
|---|
| Request body | application/json |
|---|
| Pagination | App API: cursor-based. |
|---|
| Rate limit | Track API: 100 req/sec. App API: 10 req/sec. |
|---|
| Error format | JSON: {"meta":{"error":"...","status":401}} |
|---|
Key endpoints
| Method | Path | Description |
|---|
PUT | /customers/{id} | Create/update customer |
POST | /customers/{id}/events | Track customer event |
DELETE | /customers/{id} | Delete customer |
Quickstart
PUT /api/v1/customers/user123
Authorization: Basic {base64(site_id:api_key)}
Content-Type: application/json
{"email":"user@example.com","first_name":"John"}
Agent pitfalls & tips
- Two APIs: Track (behavioral data) and App (campaigns/segments).
- Track API uses Basic auth (site_id:api_key), App API uses Bearer token.
- Customer ID is your choice — use your internal user ID.
- Events trigger campaigns (workflows) — name events consistently.
- Attributes set on customers are available for segmentation.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Customer.io's AEO score?
▼
Customer.io has an AEO score of 0.70 and is rated A (Functional agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Customer.io AI-agent-ready?
▼
Customer.io is currently connectable for AI agent use. API access is available but no dedicated MCP server has been published yet. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Customer.io compare to other Marketing services?
▼
In the Marketing category, Customer.io is rated A. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Customer.io compares.
How can I integrate Customer.io with an AI agent?
▼
The fastest way to integrate Customer.io with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Customer.io?
▼
Track API: site_id:api_key as Basic auth. App API: Bearer token from app.customer.io. Setup: 1. Go to customer.io > Settings > API Credentials. 2. Track API: use site_id and API key. 3. App API: create Bearer token for campaigns/segments.
What are Customer.io's API rate limits?
▼
Track API: 100 req/sec. App API: 10 req/sec.