get_timing_readout
The timing readout, horizon by horizon, plus how much of your book the last run actually covered. Timing is graded per horizon rather than on one number, so no single figure is synthesized across them. The score ranks the likelihood of entering a buying window within a horizon. It is not a conversion score and not a predicted close date.
What it returns
The timing model's quality readout at each horizon - AUC, the lift in the top band, whether the calibration check passed, what it trained on and the events that drove the timing - plus the last run's state and how many accounts it covered.
Credential
An app session token, from an authenticated app.ax1om.ai session. Call it with only an API key and you get a plain refusal saying so, rather than a confusing 401.
Network call: yes. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call get_timing_readout: the timing readout, horizon by horizon, plus how much of your book the last run actually covered.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_timing_readout", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.
Notes
- Timing is read per horizon. It is not a conversion score and not a predicted close date.