Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/bortlesboat/bitcoin-api/agents-mdgit clone --depth 1 https://github.com/Bortlesboat/bitcoin-apiWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00700 | $0.00700 |
| Opus 5 | $0.00350 | $0.00350 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
bitcoin-api AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Satoshi API — Bitcoin REST API (bitcoinsapi.com)
What this is
FastAPI application for Bitcoin fee intelligence, MCP-powered agents, and x402 pay-per-call Bitcoin data. The project-operated hosted deployment is intentionally paused for infrastructure review. Treat any restart or deployment as a production change and verify current operator authorization before promoting.
Architecture
src/bitcoin_api/routers/— HTTP endpoint definitions, one file per category (28 routers)src/bitcoin_api/services/— Business logic layer (HTTP-agnostic, testable in isolation)src/bitcoin_api/indexer/— Address + transaction indexer (separate worker process)src/bitcoin_api/main.py— App entrypoint, middleware, router registration, startup eventssrc/bitcoin_api/models.py— Pydantic request/response models (shared across routers)src/bitcoin_api/config.py— Settings via pydantic-settings / env varssrc/bitcoin_api/auth.py— API key authenticationsrc/bitcoin_api/rate_limit.py— Free tier rate limiting.github/copilot-instructions.md— GitHub Copilot/Coding Agent instructions for this repodocs/AGENT_INTEGRATION.md— Copy-paste kit for adding Satoshi API to other agent-aware repos
Active workflows (run these, don't skip)
./diagnose.sh— silo checks; run before any significant structural change./release.sh— tag + changelog + deploy; run for all releases./deploy-api.sh— auto-tags and deploys to production
Key rules
- Tag before major changes:
git tag v{version} && git push --tags - Run diagnose after structural changes: catches silo leaks and import errors
- All new endpoints need unit tests in
tests/ - New routers MUST be registered in
main.py— this is the #1 missed step - The hosted service is paused — do not assume hosted URLs are available or restart production from routine repo work. Test locally first.
/api/v1/rpcendpoint is used by bitcoin-mcp zero-config — don't break it
Content pages (not just API)
/history— Bitcoin History Explorer/guide— Bitcoin Protocol Guide/mcp-setup— MCP setup instructions/bitcoin-mcp— Bitcoin MCP guide/bitcoin-fee-intelligence— fee intelligence guide/quickstart— full x402 quickstart/x402/start— shortest first-paid-call x402 buyer path/docs— OpenAPI docs (/api-docsredirects here for legacy links)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 46 lines · 700 tokens per session scan A c32face86007
bitcoin-api AGENTS.md is an instructions file published in the GitHub repository Bortlesboat/bitcoin-api (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 700 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
ccxt CLAUDE.md
Claude Code instructions for ccxt/ccxt, covering ccxt — repository guide for contributors and ai agents, 1. architecture, rest vs pro (websocket), per-language model and two transpilers.
Get-Started-with-Web3 AGENTS.md
Instructions for beihaili/Get-Started-with-Web3, covering get started with web3 agent notes, 项目定位, ceo 运营目标, 常用命令 and ai-native 内容层.
raspibolt CLAUDE.md
Instructions for raspibolt/raspibolt, covering raspibolt: development guidelines, working rules, autonomy model, level 0: autonomous and level 1: inform.
ccxt AGENTS.md
AGENTS.md instructions for ccxt/ccxt, a project described as: A unified trading API with more than 100 crypto exchanges and prediction markets in JavaScript / TypeScript / Python / C# / PHP / Go / Java.
bitcoin-mcp copilot-instructions.md
Instructions for Bortlesboat/bitcoin-mcp, covering bitcoin-mcp copilot instructions, rules, satoshi api reference and verification.
bitcoin-mcp AGENTS.md
Instructions for Bortlesboat/bitcoin-mcp, covering bitcoin-mcp — mcp server for bitcoin, what this is, key files, tool categories (all in server.py) and development rules.