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/copilot-instructionsgit 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.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
bitcoin-api copilot-instructions.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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Satoshi API Copilot Instructions
Satoshi API is Bitcoin fee intelligence for agents and developers. Lead with outcomes: save money on fees, know when to send, and stop watching block explorers. Avoid selling the product by endpoint counts.
Project Shape
- FastAPI app in
src/bitcoin_api/; routers are thin HTTP wrappers and business logic belongs insrc/bitcoin_api/services/. - Canonical public API paths use
/api/v1. Keep generated clients on/api/v1. - The only versionless paid aliases are the x402 hero paths:
/fees/landscape,/mining/nextblock,/fees/observatory/scoreboard,/ai/fees/advice, and/ai/explain/transaction/{txid}. They must stay hidden from OpenAPI and priced by the same x402 rules as their canonical endpoints. bitcoin-mcpuses/api/v1/rpcfor hosted fallback. Do not break anonymous read-only RPC fallback without updating the MCP docs and tests.
x402 Buyer Path
The project-operated hosted deployment is intentionally paused for infrastructure review. Treat the URLs below as deployment contracts, not live smoke-test targets, until the repository status notice is removed.
- First paid-call page:
https://bitcoinsapi.com/x402/start. - General quickstart:
https://bitcoinsapi.com/quickstart. - Discovery:
https://bitcoinsapi.com/.well-known/x402andhttps://bitcoinsapi.com/openapi.json. - Payment headers: unpaid responses return
PAYMENT-REQUIRED; paid retries should usePAYMENT-SIGNATURE; successful paid responses includePAYMENT-RESPONSE. - x402 uses USDC on Base. Runtime wiring lives in the
bitcoin-api-x402extension package. - Runnable buyer examples live in
examples/x402-paid-call/paid_call.pyandexamples/x402-paid-call/paid-call.ts.
Agent/MCP Integration
Use docs/AGENT_INTEGRATION.md when adding Satoshi API to another repository's agent instructions. Minimal MCP config:
{
"mcpServers": {
"bitcoin": {
"command": "bitcoin-mcp"
}
}
}
Set SATOSHI_API_URL=https://bitcoinsapi.com only after the hosted-service status has been verified active. Use a self-hosted base URL while the pause is in effect.
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 · 52 lines · 660 tokens per session scan A 52d95f71ae4f
bitcoin-api copilot-instructions.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 660 tokens to every session, about $0.0033 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
Get-Started-with-Web3 AGENTS.md
Instructions for beihaili/Get-Started-with-Web3, covering get started with web3 agent notes, 项目定位, ceo 运营目标, 常用命令 and ai-native 内容层.
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.
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.
raspibolt CLAUDE.md
Instructions for raspibolt/raspibolt, covering raspibolt: development guidelines, working rules, autonomy model, level 0: autonomous and level 1: inform.
cashu.me AGENTS.md
Instructions for cashubtc/cashu.me, covering cashu.me developer guide for agents, 1. tech stack, core frameworks, mobile & desktop and cashu & cryptography.