Payment happens without a checkout page, which is the point of x402 and also the risk: whatever drives this server can spend from the configured wallet. Fund it with what a research session is worth and no more. Two of the three tools cost nothing — searching and browsing are free, and only retrieving a full report triggers a payment.
A pay-per-use content server: an agent searches curated reports drawn from live Twitter Spaces, and unlocking a full report triggers an x402 payment that is split on-chain between the host, the curator and the platform.
- `search-reports` and `browse-reports` to find timestamped, curated reports by topic
- `get-report-resource` to retrieve the paid content once payment clears
- Reports carrying key quotes and topic summaries, bullish or bearish sentiment classifications, speaker breakdowns, narrative tags, and links back to the original audio
- Automated revenue distribution on each payment — 50% to the host who ran the Space, 30% to the curator who produced the report, 20% to the platform
Run from a checkout: clone the repo, `npm install`, copy `.env.example` to `.env`. The MCP side needs `PRIVATE_KEY` — the wallet that pays for reports — and is launched as `node dist/x402McpServer.js`. Running the payment server too means supplying CDP smart-account credentials (`CDP_API_KEY_ID`, `CDP_API_KEY_SECRET`, `CDP_WALLET_SECRET`), the payout addresses, and a USDC contract address; `npm run start:express` serves it on `http://localhost:4021`.
Build from source — clone the repository and build it, then point your client at the binary