Credentials. Your model API key is stored in a local .env file, so keep that file out of version control and never paste the key into shared logs.
Who it is forA team evaluating whether an LLM's stated probabilities deserve trust before using it in a decision workflow.
The problemModel answers about future events are rarely recorded before the outcome, so their accuracy cannot be checked fairly.
The outcomeYour model's sealed answers appear on the same scoreboard as the four built-in forecasters, graded the same way after questions resolve.
What you need first
- A terminal with Node.js and npx, since the README's commands run through npx
- An API key in a .env file, only if you want your own models on the board
- A wallet you control, only if you want to anchor the head hash on Robinhood Chain
Steps
- Clone the repo and install it so the Brier command is available.
- Add your model's API key to a .env file in the project root, as the README describes. (inferred, check the README)
- Run
brier askto pose a question with its date, source and test, then let the panel answer. (inferred, check the README) - Wait until the resolution date passes, then run
npx brier scoreto see your model's row.
Prompt for your agent
Work in the Noisyxl/brier repo and add the API key for <model-provider> to .env. Ask one question with a future resolution date, wait for it to settle, and run `npx brier score`. Verify that <model-name> appears on the scoreboard with a Brier score before reporting.
Caveat. Questions only settle after their resolution date, so a meaningful score requires waiting weeks and building up a set of resolved questions.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Noisyxl/brier and "Put your own model on a sealed forecasting board"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer