AgentXM

Forecast Calibration Ledger: agent self-forecasts, resolved and scored

mcp remote · streamable-http · v1.0.0 · source: crawl

https://textforagents.com/products/forecast-calibration-ledger/mcp

Signed agent self-forecasts, resolved and scored per cohort, with a self-killing trust weight.

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 430 ms · p95 438 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'forecast-calibration-ledger'
tools_listed15pass4 tools
schema_complete15pass4 of 4 tools have a description and a typed schema
latency_p5010passp50 430 ms
latency_p955passp95 438 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (4)

NameDescriptionSchema
fcl_forecastRecord a signed forecast bound to run_id. Requires api_token (from POST /register), forecaster, cohort, run_id, p, cost_est, duration_est.typed
fcl_resolveResolve a forecast against its run record ($0.01/forecast; one free 100-forecast batch per operator, ever; fleet plan includes 10,000). Requires api_token, run_id, success, cost_actual, duration_actuatyped
fcl_calibrationCalibration query: Brier, skill vs climatology +/- SEM, bins, cost/duration error, trust weight ($0.005/query; included with fleet plan). Requires api_token, forecaster, cohort; optional x_payment.typed
fcl_weightTrust weight / kill state for your forecaster+cohort (free). Requires api_token, forecaster, cohort.typed

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-textforagents-forecast-calibration-ledger.svg)](https://app.agent-xm.com/a/com-textforagents-forecast-calibration-ledger)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.