Developer & API
AXO gives developers and AI agents four ways to integrate. Every operation your team runs in the app is reachable programmatically — over MCP for conversational agents, over REST for your backend, from the browser tag, or via server-side ingestion. Full request/response examples and the complete tool list live in the structured API reference; this page is the map.
MCP server — for AI agents
Connect Claude or any MCP client to AXO's hosted endpoint and operate personalization through 130+ tools — analytics, segments, variants, placements, triggers, profiles. Scoped tokens, no local install. See the MCP connection guide and the full tool reference.
REST API (Pulse v1) — for your backend
Read profiles and segment membership from your own systems at decision time — no ETL, no stale copies. Bearer keys, scopes, cursor pagination, and a published OpenAPI 3.1 spec. See the REST reference.
Tag JS API — in the browser
The window.axo API (identify, convert, setCart, getSegment, …) plus data-vt-* authoring attributes. See the tag reference.
Ingestion & webhooks — server-side
Send identify / convert / lead events from a server or headless stack, and receive HMAC-SHA256 signed webhooks for profile.identified, segment.changed, and conversion events. See ingestion & webhooks.