create_timing_model
Configures the in-market timing model: for each account, when it is likely to enter a buying window, learned from your own account event history. One per workspace, so calling it again reconfigures the existing model rather than creating a second. Returns the model id and the resolved configuration.
One timing model per workspace, and timing is included with Pro and above.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
connection_id | string | Yes | |
provider | string | Yes | |
hand_raisers | any | No | |
horizons | any | No |
What it returns
The timing model's id and status, the configuration it was set up with, the validated contract, and the ways timing deliberately works differently from the other model families.
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 create_timing_model: configures the in-market timing model: for each account, when it is likely to enter a buying window, learned from your own account event history.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_timing_model", "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 cannot be asked for one account on demand: it refreshes on a dispatched run rather than per request, so live scoring refuses a timing model instead of returning a number that would be stale by construction.