Get your facts on a ticker and what each did
get_gambit_factsYOUR facts on one ticker and what each did to your own view (requires api:read) — the call for "what have I added on INIT?" or before removing one. The chain for one ticker. Everything it stores is in YOUR personal layer: the shared view never changes because of it. Gambit forms your view on its side: you do not need your own model for it. (1) Add data: add_gambit_evidence stores a fact you know. It is labelled unconfirmed until Gambit confirms it from an official or wire source that states it; a confirmed fact's source joins the shared evidence, and the shared view uses it on its normal run. (2) Your view: your own take, which Gambit keeps for you. It starts as the shared take. Each fact you add, each new shared version and each update you ask for moves it: Gambit's per-story step judges your new facts and the shared news since your last update against your take and applies its verdicts. A fact that changes a lever adds a test to your take: wrong if the fact is not confirmed by its check-by date. A fact that expires unconfirmed after its check-by date leaves no trace: when Gambit had set it aside (it moved nothing), your view stays as it is; otherwise your take points back to the shared take and Gambit applies your remaining facts again on it, and with no fact left you follow the shared view. remove_gambit_evidence takes one fact back; reset_gambit_view takes back every fact. When your take ends up the same as the shared one, you follow the shared view again. To use your own model's view instead (optional): call get_gambit_pack, form the take with the rules and output_schema in the pack, then call submit_gambit_view; Gambit then moves that view the same way. (3) What if: what_if_gambit gives the view if something happened; when the question matches a dated condition the view already lists, the answer is precomputed and no model runs; otherwise it returns the pack with the event added, for your model to answer. (4) Plan: plan_gambit gives entry, stop, size and exits from your own limits. A plan is not a recommendation to trade and places no order. Returns facts: your active facts (unconfirmed or confirmed; expired and removed ones are not listed), the newest 50, oldest first, each with user_item_id (pass it to remove_gambit_evidence), claim, url, status, created_at, check_by, effect (what it last did: effect, target and target_name, the lever it moved or was set aside from, direction, set_aside_reason, and lean_move when it moved your view; null before Gambit has stepped it) and filing (the SEC filing passage the fact cites: company, form, filed, quote, source_url, status confirmed or sourced; null when it cites none); and follows (own when your view is your own, gambit when it is Gambit's). A fact the per-item step logged as a new lever has not moved your view yet: it waits for a full review. Errors: 409 gambit_building when Gambit has no view of the ticker yet (get_gambit by symbol queues it; try again later); 404 unknown_symbol; 422 ambiguous_symbol with candidates (call again with one candidate as the symbol); 503 gambit_personal_disabled while the personal layer is switched off. Gambit runs no model for this call.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"symbol": "<symbol>"
},
"name": "get_gambit_facts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | a ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit |