check_timing_validation
Grades the timing model per horizon on its own holdout evaluation. Deliberately not the forward backtest check_validation runs for a scoring model: what you get is what the engine computed, with the horizons it could not grade named as such rather than filled in.
What it returns
The timing model graded on its own holdout evaluation - AUC and top-band lift at each horizon, the calibration check and the feature-stability reading - with the horizons that could not be graded named as such.
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 check_timing_validation: grades the timing model per horizon on its own holdout evaluation.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "check_timing_validation", "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.