trackBTC.bot is an agentic Bitcoin intelligence layer.
trackBTC.bot is now available in alpha. The API is available on a limited basis for selected review and integration partners. For restricted access or schema review, please reach out.
Why it exists
trackBTC began as a Bitcoin explorer. Its broader goal is to make an agentic Bitcoin experience first class.
Most Bitcoin interfaces are built for human lookup: blocks, transactions, addresses, balances, charts, and manual interpretation. Useful as they are, the next generation of Bitcoin software requires structured, reliable, high-context access to Bitcoin state for AI agents.
What agents need to understand
- address behavior
- UTXO shape
- wallet topology
- consolidation opportunities
- accumulation and distribution patterns
- exchange-like wallet behavior
- historical spending behavior
- operational flows across clusters
- signals relevant to custody, wallets, proof of reserves, and treasury operations
The direction
trackBTC.bot is being built as that intelligence layer, giving agents near-real-time access to the context needed to reason about Bitcoin activity, explain what is happening, and eventually help users operate wallets more safely.
This means moving beyond passive dashboards toward agentic Bitcoin software where tasks such as UTXO consolidation, wallet hygiene, posture analysis, proof-of-reserves support, and Lightning-aware transfer workflows can be planned, explained, simulated, constrained by policy, and executed securely.
For example, an agent should be able to detect that a wallet has an inefficient UTXO shape, explain why that matters, propose a consolidation plan, estimate the operational tradeoffs, and simulate the result.
But it should not be able to execute that plan just because it generated a recommendation.
Approval boundaries
Execution should require explicit policy approval, signing authorization, audit trails, and clear separation between analysis, recommendation, and action.
Security is critical. Agentic Bitcoin systems cannot be black boxes; they require deterministic workflows where appropriate, strong guardrails, explicit approval boundaries, auditable reasoning, cryptographic evidence, and clear separation between analysis, recommendation, and execution.
That is the design direction behind trackBTC.
Alpha limits
The alpha release is intentionally limited. While the underlying system and API support real-time operation, full access is not yet available, and some data, including address-level details, remains redacted during testing, validation, and due diligence.
This is intentional. The alpha should not be treated as an authoritative source of truth or relied upon for production, compliance, trading, custody, or operational decisions.
What comes next
For now, the focus is gathering feedback on the analysis model, interface, data presentation, and the types of Bitcoin intelligence people want agents to access.
Over time, trackBTC will expose an API layer for applications that need Bitcoin intelligence directly within proof-of-reserves systems, mobile wallets, light Bitcoin clients, custody workflows, and agentic wallet operations.
Feedback is welcome from teams working on Bitcoin wallets, custody, Lightning, proof of reserves, on-chain intelligence, or operational AI systems.