AI: orchestration
AI orchestration ties the three together: the engine detects the moment in user state, picks the cohort, and chooses the action, so the loop runs without you wiring each step by hand.
At a glance
- GraphQL
aiquery: summarise, explain, suggest- MCP
- Every
prodantix.*tool, callable by an agent - MCP host
https://eu.mcp.prodantix.com- Auth
- Access token
- Detects the meaningful moment in live state
- Selects the right cohort and the right action
- Closes the loop: the action becomes the next event the engine learns from
How it works
Every answer is grounded in rows the caller could already read. Citations are resolved server-side from a built candidate list rather than taken from the model’s reply, so an answer can only point at something that exists and the caller is entitled to see.
Where to reach it
| Surface | Operation |
|---|---|
| GraphQL | ai query: summarise, explain, suggest |
| MCP | every prodantix.* tool, callable by an agent |
Example
GraphQL
query Explain($projectId: String!) {
ai {
explainMetric(
projectId: $projectId
metric: "order.completed"
window: "P7D"
) {
summary
citations { kind id }
}
}
}Pointing an agent at prodantix
The MCP surface exposes the same capabilities to an autonomous agent. See MCP for the tool list and protocol details.
JSON
{
"mcpServers": {
"prodantix": {
"url": "https://eu.mcp.prodantix.com/mcp",
"headers": { "Authorization": "Bearer <access token>" }
}
}
}