Surfaces: MCP Server, CLI, API & SDK | iCustomer
Surfaces, One Platform, Every Interface
Work with iCustomer wherever you work.
iCustomer exposes one governed toolset through four surfaces: MCP for your agents, a CLI for your terminal, an API for your services, and SDKs for your codebase. Same audiences, same guardrails, same Decision Traces, whichever door you use.
MCP
MCP Server
Connect your AI agents to your audience.
- Audiences, FIRE scores, decisions, and activations exposed as governed tools
- Works with Claude, Claude Code, Codex, and Gemini out of the box
- iHarness guardrails and consent checks on every call; every action leaves a Decision Trace
CLI
CLI
Deploy loops from your terminal.
- Ship decision loops as code; config versioned in git
- One-command deploys from Claude Code or Codex sessions
- Same loops, headless: everything the app runs, scriptable
API
API
REST access to audiences and decisions.
- One API to every connected tool: 200+ integrations behind one endpoint
- Audiences in, next best actions out, with PII and leak protection on every payload
- iConnect routes each decision to whichever tool should execute it
SDK
SDK
Client libraries for your stack.
- Typed clients for the API and event capture
- Server-side pixel and signals capture for web and commerce
- Public examples and loop configs in the open repo
Turn your data into outcomes
Start free with Audience Loop. Or talk to us about a Composable Decision OS pilot on your warehouse.