Overview
Prodantix is a single engine that holds one source of truth about every user (their live user state) and lets you observe it, decide on it, and act on it without gluing separate analytics, flags, messaging, and data tools together.
Most stacks fragment the same user across four products. Every handoff loses fidelity and adds lag. Prodantix keeps all four on one continuously-updated state: the view, the decision, and the action all read the exact same truth, in real time.
At a glance
- Hosts
- Five, across REST, GraphQL, Socket.IO and MCP
- Credentials
- Project key for ingestion, access token for the application model
- Data residency
- EU for ingestion and replay
- Start here
api.prodantix.com/graphql
The surfaces
Each surface has its own host and accepts its own credential. Project keys open the event and flag paths; access tokens open the administrative surfaces.
| Host | Protocol | Credential |
|---|---|---|
| api.prodantix.com | REST (flags, messaging) · GraphQL · GraphiQL | Project key · Access token |
| eu.api.prodantix.com | REST (event ingestion) | Project key |
| eu.replay.prodantix.com | REST (session replay) | Project key |
| eu.ws.prodantix.com | Socket.IO realtime | Access token |
| eu.mcp.prodantix.com | MCP (JSON-RPC 2.0) | Access token |
Where to go next
- Projects & keys: sign up, create a project, copy its keys
- Quickstart: install an SDK and send a first event
- Concepts: event, user state, decision, action
- REST: base URLs, the eight operations, the OpenAPI documents
- GraphQL: the full application model, plus the playground
- Realtime: Socket.IO rooms and events
- MCP: the nine tools an agent can call
- API reference: every operation, rendered