Rates
A free desk, three plans, and a wire that takes coins.
The wire's atomic price is $0.030 a dispatch, settled on-chain over x402 — no account needed. Plans are prepaid dispatch bundles at volume discount; holding $MHB issues the same credentials automatically. No sales calls: this desk is a correspondent and its owner, and the meter is public.
Plans
Starter
Press pass. Free forever.
- 10,000 dispatches/month (bursts to 300/hr)
- Crypto, finance, tech — real time
- Turkish markets — second edition (24h)
- WebSocket stream included
- Full-text search · sentiment · importance
- Community support
Builder
For products shipping on the wire.
- 150,000 dispatches/month (1,000/hr)
- Everything in Starter
- Turkish markets — first edition, real time
- Telegram alert bot
- Priority queue position
Growth
For desks that trade on it.
- 300,000 dispatches/month (5,000/hr)
- Everything in Builder
- Advanced analytics API
- Entity timelines
- Webhook delivery
- The desk answers — async, honest latency
Syndication
License the wire. Custom terms.
- Custom volume (50,000/hr ceiling)
- Everything in Growth
- Custom rate, format and delivery terms
- Uptime is public — verify the wire probe
- Credentials are self-serve: stake or spend
Stake instead of subscribing — hold $MHB
Sign in with the wallet that holds $MHB and the plan sets itself — checked on-chain at login, upgraded and downgraded automatically. No card, no renewal; sell the tokens and the tier simply lapses. Metered spend bridges too: a month of x402 calls at or above a plan's price earns that plan on the same wallet.
Metered — pay per dispatch, no account
The agent routes accept x402 payment on 0G — USDC.e via EIP-3009 or W0G via Permit2, settled before the response is served. Your first uncredentialed call returns the exact terms.
import { wrapFetchWithPayment } from "x402-fetch"
const paidFetch = wrapFetchWithPayment(fetch, walletClient) // 0G chain 16661
const res = await paidFetch("https://api-production-ba80.up.railway.app/v1/news?vertical=crypto")Compare
The probe is public and live at muhabbit.com/status → — every plan gets the same measured truth.
The archive — point-in-time history
Every dispatch is stored with two clocks — the publisher's timestamp and the wire's ingest time — and event classification is deterministic, so a backtest over the archive sees exactly what the live stream saw. No look-ahead, by construction.
Archive terms: sales@muhabbit.com
Questions the desk gets
What does a Syndication license actually cover?
Republication rights for the wire's own output — headlines, summaries, sentiment, and translations — in your product, under your custom volume, format, and delivery terms (feed, webhook, or bulk). It never includes the source articles themselves (we license our work, not theirs) and the agent stays sealed: terms cover output, not the corpus or the models. Write to the desk with your volume and locale; terms come back as a one-page schedule.
Can I upgrade my plan later?
Yes — and mostly by machine: holding $MHB upgrades the plan at wallet login, and a month of x402 spend at or above a bundle's price earns it automatically. The desk only needs to hear from you for Syndication terms.
What happens when I hit my limit?
Requests beyond your limit receive a 429 with Retry-After. Nothing is silently dropped; upgrade any time for higher limits.
Is Starter really free?
Yes. 10,000 dispatches a month, no card. Sign in with a wallet and the key is minted on the spot.
What does Türkiye coverage include?
BIST analysis, TCMB announcements, Turkish crypto exchanges (BtcTurk, Paribu), Turkish-language reporting from major outlets — translated and scored like everything else on the wire.
How does paying per call work?
The x402 routes take on-chain payment instead of an account: your first call returns 402 with the exact terms, your client signs a USDC.e (EIP-3009) or W0G (Permit2) transfer on 0G, and the dispatch is served the moment it settles.
How does webhook delivery work?
Growth and Syndication can subscribe to real-time events (article.created, article.approved, …) delivered to your endpoint with HMAC signature verification.
Something else? Write to the desk →