Structured wallet-change data, exposed carefully.
Isobath has structured wallet-change data today. The public API and MCP server are not live yet because supported integrations create support, uptime and pricing obligations. For now, the product pages, Daily Tape, feed, llms.txt and sample schemas are the public machine-readable layer.
Current access
Use the public market pages, wallet records, rotation view, heatmap and Daily Tape to inspect the data today. Signed-in users can also watch wallet-market pairs and receive Telegram alerts when new material changes appear.
What the data is
Isobath turns observed Hyperliquid wallet state into canonical change events: position opened, closed, increased, reduced, flipped, or a material collateral change. Each event carries asset, wallet address, before/after values, side, observed rank and share where available, observation window, coverage, and timestamp.
{
"type": "position_increased",
"asset": "BTC",
"wallet": "0x004edc...6c1bb8",
"side_after": "long",
"notional_before_usd": 7800000,
"notional_after_usd": 35100000,
"observed_asset_rank_after": 5,
"observed_asset_share_after_pct": 5.51,
"coverage_after": 0.333,
"observed_from": "2026-08-27T02:12:00Z",
"observed_to": "2026-08-27T04:12:00Z"
}
Agent-readable public resources
Search engines and AI agents increasingly discover products by reading structured public pages, not only homepages. Isobath supports that layer with clear sitemap entries, structured data, a Daily Tape archive, an RSS/Atom feed, llms.txt, and static sample schemas for canonical events and wallet history.
A future data product would expose the same canonical events and wallet history the web product already uses — not a separate black-box signal feed. Likely surfaces: API, webhooks, historical exports and documented sample datasets.
MCP access belongs on top of the same canonical data layer, so AI agents can ask grounded questions such as "which large SOL wallets reduced exposure today?" without seeing internal collection machinery.
Limited case-by-case exports may be considered before a public API, with a clear support boundary and explicit commercial agreement. Get in touch -- until then, the public product is the supported surface.
Developer surfaces not available yet
Data questions
Please don't — scraping is not a supported integration path and can affect service for other traders. Public agent-readable artifacts exist today; a full API or MCP contract comes later.
Not decided. Public pages and some sample artifacts should remain open. Reliable programmatic access, deeper history, bulk exports and higher-volume workflows are likely commercial surfaces.
Internal collection machinery. Developer surfaces should expose canonical events, coverage, timestamps and wallet histories — the same intelligence the product shows, packaged safely.