Define the decision before choosing the feed
Consider a recurring task: read a Fed contract, explain what would satisfy it, estimate the cost of 500 YES shares, then return after the relevant publication. A price feed answers one part. The agent also needs to know whether the market refers to the upper target bound, how the terms handle an unusual move, and what happens if no statement appears.
Those are checkable questions. The useful output is an answer with enough retained context for another process or person to inspect it. A long tool catalogue, many requests or fluent prose do not demonstrate that the requested job was completed. Decide what an acceptable answer must contain before adding another data integration.
Bind every answer to an exact contract
Event names are convenient navigation; exact market identifiers define what is being examined. An event can contain several outcomes, and two similarly titled markets can have different dates, thresholds or exceptions. Keep the native URL, captured contract ID and selected outcome through search, evidence, cost and saving.
The conditions need more than a paraphrased headline. Retain the measurement, comparison, deadline, fallback and unresolved wording with source references. Where HowSure recognizes complete supported terms, its deterministic reading makes these explicit. Unsupported wording stays unsupported. A nearby template is not permission to fill in missing conditions.
A number needs a period and a publication version
A GDP contract may require the advance estimate for one quarter; a later revised number answers a different question. A monthly PCE question needs the reference month and core monthly measure, which can differ from the headline annual figure displayed prominently on an overview page. The document’s identity is part of the result.
Keep the source URL, relevant passage, locator and observation time, along with any printed publication time or version limitation. Downloading an old release today does not prove that its bytes are unchanged from first publication. A changed URL does not prove the value was revised. If the required vintage or seasonal basis is not established, that uncertainty belongs beside the number.
Price the requested size and keep its clock
A midpoint is not the cost of buying 500 shares. Read the chosen side’s depth, calculate the filled quantity across available levels and show any unfilled remainder. A partial fill does not justify extrapolating a price for the missing shares. A missing fee schedule means unknown fees, not zero fees.
A useful estimate retains share units, gross notional, fees, total for the covered quantity and whether a total for all requested shares is available. It also carries the book’s observation time, response freshness evidence where available and fee-model expiry. YES and NO requests can observe different moments. Neither a snapshot nor a recent HTTP response guarantees execution.
In the current HowSure task recipe, books remain local dated receipts. Saving source evidence does not put those quotes into the research document, and a source recheck does not refresh them. Ask for a new book when the next task needs a current cost.
Make the next answer explain the difference
Save an exact evidence version and keep its IDs outside the chat. After restart, the agent can retrieve that same basis and request a new comparison. This supports a specific answer: which passage changed, whether the reported fact changed, which condition it may affect and what could not be read.
Treat changed, unchanged, cached, incomplete and unavailable as different states. A failed request cannot establish that nothing happened. A correction to HowSure’s earlier interpretation is another separate input, represented by correctionReview. Preserve the original answer and decide explicitly whether to create a new conclusion; do not silently adjust an author’s probability.
Keep the answer short without losing the evidence
The agent does not need every repeated passage in its first view. HowSure 0.1.50 provides an explicit compact projection of conditions, facts, changes and unknowns, with the full operation response accessible separately. Exact identity, source period/version and clocks still matter. A partial book keeps its unfilled quantity and unknown fees; a failed or cached source read cannot become a fresh unchanged finding.
For MCP, a process-local resource returns the same full response for up to 15 minutes, subject to receipt and byte limits. It is not durable after restart. CLI writes the full basis to a new local file; the JavaScript caller keeps its raw object. Retain the full evidence before saving or restarting. The projection is deterministic and does not call a model. Smaller output is an integration property, not proof of a better answer or lower total task cost.
Evaluate the complete task
Give your agent a contract it actually needs, then examine its first answer and later return. Check identity, cited conditions, source version, numerical units, partial depth and treatment of unknowns. Record errors, elapsed time and any manual repair. A valid JSON shape is useful for integration; it is not proof that source text is authentic or that a forecast is correct.
HowSure 0.1.50 supplies the inspect, explicit save, exact-version read and recheck path through existing client operations. It does not require HowSure to call a paid model. Your host may use its own model under its own settings. Public source access, supported contract scope and service limits still apply. The practical question is whether this evidence helps complete your recurring task accurately enough to use again.
Sources & verification
- HowSure end-to-end agent task and limits
- Exact source evidence and cost response contracts
- Published October Fed conditions review
- Dated 500-share response used in the cost guide
Sources and instructions checked 18 October 2026. Live responses can change. Editorial method and limitations.