MorScan: the Morpheus network explorer, source-open
The full history of the Morpheus compute marketplace: providers, sessions, bids, and price, read from chain. Signed API, CC0 dataset, agent-native.
MorScan is real-time intelligence on the Morpheus compute marketplace: which providers are live, what models they bid, where sessions are flowing, and what the token is doing. The indexer, the dataset, and every signed observation are open.
If you stake MOR, run a provider, or build on Morpheus, this is the one place the whole network is legible.

The whole tape
The indexer reads the Morpheus compute, builder, and token contracts on Base and derives the full history from chain: 113,000+ inference sessions, every model bid ever posted (403, decoded from `MarketplaceBidPosted` events), 21 providers, 14,500+ MOR holders classified by on-chain role, and the complete MOR/USD price history from the pool's first block in September 2024. No 90-day window, no gaps: MorScan replays the whole tape.
Price now reads straight from the MOR/WETH pool on-chain at each block, computed from the pool reserves and a Chainlink ETH/USD reference, instead of a CoinGecko feed. One fewer third-party dependency, and exact to the DEX the token actually trades on.
The RPC failover under the indexer is its own open release: drm3-rpc-pool, if you want to squeeze 10x the juice out of your free RPC tiers.
Check any response in one command
Every API response is signed with an Ed25519 provenance receipt at the moment it is served. The keys are published at /.well-known/morscan-keys.json. Checking a response takes one command:
Fifty lines of Node, standard ed25519, no DRM3 code required. Tamper one byte and it fails. The signature covers the what. The source covers the how. Not a terminal person? morscan.io/verify runs the same check in your browser and walks you through every step: your own machine does the math.
git clone https://github.com/DRM3Labs-OSS/morscan.io && cd morscan.io
npm install && npm run verify:receipt
PASS: rcpt_cf69632391c08ee0 (blockchain.price) from https://morscan.io/mor/v1/price
key: published as morscan/cache (current)The dataset is yours
The full database ships as a signed, portable snapshot under CC0, published as its own project: morpheus-ai-base-data. Fifteen SQLite tables: sessions, holders, providers, bids, price history. Be clear on what it is: a point-in-time capture from the first block up to a daily high-water mark, so it lags live by about a day. Today is not in it; the most recent complete day is yesterday. For live data you hit the API; for a bulk local copy you take the snapshot. Query it with SQLite or DuckDB and never touch MorScan at all, or import it to fast-forward a fresh install and let live sync fill the delta from the watermark. It is re-derivable by anyone from Base, which is the point: if we disappeared tomorrow, the data would not.
A key is one signature
Connect a wallet, sign a challenge, and the key is issued. No email, no signup, no payment. 60 requests per minute free with daily and monthly volume caps. Staking MOR on the MorScan builder subnet raises the caps: capacity follows your stake, read live from the indexed chain state, and comes back when you unstake. Price and health are public and unmetered.
curl -s https://morscan.io/mor/v1/providers -H "X-Morscan-Key: mor_yourkey"Agents are first-class
An AI agent landing on morscan.io can discover, authenticate, and pay without a human: `llms.txt`, markdown negotiation, an RFC 9727 API catalog, published agent skills, and the same wallet-signature key mint, fully headless. No wallet at all? MorScan speaks x402, and payments settle on-chain: a keyless call to a metered endpoint returns a priced USDC-on-Base payment envelope instead of a dead end; pay it and the API answers, with settlement landing on Base. Agents that want volume buy a call pack the same way: one payment, one on-chain settlement, a metered key with a perpetual balance.
Why we built it
This one is for the Morpheus community. DRM3 uses Morpheus in production: our news pipeline and other workflows route inference through the network, and we run a subnet on it. When you build on something and stake into it, you want to see it clearly, which providers are live, what models they bid, where sessions are flowing, what the token is doing. There was no single place for all of it. So we made one, and opened it up.
Fair Source
The repo is public under FSL-1.1-MIT, Sentry's Fair Source license: fork it, run it, verify it. The deal: no competing hosted service for two years, and every release becomes MIT after two years, guaranteed.
morscan.io itself runs the Sentry model with a twist. The site is the exact public core, pinned at a tag, composed with private commerce and analytics plugs behind documented sockets; the same sockets anyone can implement. /version is the receipt: it names the core tag and commit actually running, and anyone can diff that against GitHub. Issues and pull requests are welcome, and we mean it: the core that runs the site ships for everyone.
Alpha software. Numbers are derived from on-chain events and served as-is; the receipt lets you check any of them.
Formerly Cashew. The old address redirects, and nothing you bookmarked breaks.
Disclosure: DRM3 Labs holds and stakes MOR and sells MOR-denominated products.
Published by
Robert Christian
Founder and CEO, DRM3 Labs Corp.
More from DRM3 Labs
TruthFoundry 1.9: yesterday's paper is still the paper
Robert Christian · 2 min read
DomainDrift 1.18: the evidence bundle becomes a product, and a public index of who speaks MCP
Robert Christian · 3 min read
DomainDrift 1.17: plug an AI agent straight into signed internet telemetry
Robert Christian · 3 min read
2026 DRM3 Labs Corp. All rights reserved. DRM3 Labs builds infrastructure for open protocols.
This article is for informational purposes only. Nothing here is financial, investment, or legal advice. Tokens, staking, NFTs, and blockchain protocols are described as technical mechanisms, not investment recommendations. Digital assets carry risk. Do your own research.
Many DRM3 products mentioned are in early alpha. Features, availability, and economics are subject to change. References to the Morpheus network describe the public protocol as documented at mor.org.
