Hunter — Documentation

Crypto intelligence you can own. $DRPXBT · Base

Hunter is an autonomous crypto-intelligence platform: a research agent with a public, verifiable signal track record, an OpenAI-compatible inference API to open-weight models (routed through OpenRouter today; owned hardware planned — see §08 for what that means for privacy right now), a daily audio briefing, and one web3 app where all of it lives.

Read this as a website: https://huntertheagent.github.io/hunter-docs/

🖥️ App	hunter-terminal — chat, signals, podcasts, API keys, access, usage. Not yet publicly deployed; run it locally with hunter-demo.
🌐 Site	drpxbt.xyz
🚀 Run the stack	hunter-demo — the whole platform from one compose file
⛓️ Contracts	hunter-contracts

What's here

Section	What it covers
Litepaper	What Hunter is, what $DRPXBT does, how the revenue flywheel works, and the disclosures that come with it
Architecture	The as-built system: context, components, runtime flows, data model, interface contracts, on-chain design, deployment, security & privacy, observability, and the decision log (ADRs)
Brand	The reticle mark, palette, logo suite and deck template

How the platform fits together

        drpxbt.xyz ──▶ the app (hunter-terminal)
                              │
              ┌───────────────┼───────────────┬──────────────┐
              ▼               ▼               ▼              ▼
        hunter-agent    hunter-gateway   hunter-platform  hunter-podcast
        chat, pipelines  inference API    entitlements,    daily briefings
        ACP, SIWE        hk_live_ keys    signal record
              │               │               │
              ▼               ▼               ▼
         hunter-mcps    self-hosted      Postgres + pgvector
         tool plane     open models
                              │
                              ▼
                   hunter-contracts (Base)
              TierLock · Staking · Subscription
              RevenueSplitter · Buyback

Every repository in the platform, with its role and quickstart, is listed in the architecture components doc.

Principles

• Receipts over claims. Signals are published before outcomes are known and scored afterwards by an independent job. The scoreboard is public and nothing is deleted.
• Privacy is a product feature. Prompts are not stored by default; the usage ledger records token counts, never content. Retention is opt-in per API key.
• Open by default. The stack runs end to end from a single compose file, and the interfaces are documented down to the contract level.

Contributing to the docs

Every page has an "edit this page" link at the bottom. The site is generated by site/build.py (python-markdown + one template) and deployed by GitHub Actions on every push to master. To preview locally:

pip install markdown && python site/build.py && open _site/index.html

Conventions for PRs are in the org CONTRIBUTING guide.

---

Nothing in this documentation is financial advice. $DRPXBT is a utility token that gates access to the platform. See the litepaper's disclosures.