Skip to main content
Seven surfaces. The list is closed and governed by the Glossary. A new place Shumi appears gets added there before it is used anywhere else.

​
The seven

Shumi Web. The main product, on shumi.ai. Full chat, widgets, the deepest rendering of any surface. The default answer to “where do I use this”. Shumi Search. An embedded AI entry point inside the search flow. Same pipeline, entered from a query box rather than a conversation. Shumi Telegram. Fast, low-bandwidth, operator-shaped. Text only, no widget rendering, answers condensed to fit the format. Best for checks, worst for analysis. Shumi API. The typed HTTP surface. Everything else on this list is a client of it. See API Overview. Shumi CLI. npm i -g shumi. Terminal and scripting, auto-JSON when piped, and where you mint API keys. See CLI. Shumi Landing. Entry, positioning, and studies on shumi.ai. You read about the product here; you use it on Shumi Web. Shumi Realtime. The live data layer underneath the user-facing surfaces. Not a destination, no public URL, and you never visit it. It shows up in these docs because it is what makes live trend history live.

​
Picking one

​
Domains are not surfaces

Three surfaces share shumi.ai and one has no domain at all, which is why the two ideas are kept separate. “The site” is not a surface name, and neither is “the dashboard” or “the bot”. MCP is likewise not an eighth surface. It is a transport for Shumi API. coinrotator.app is a different product on the same data; see CoinRotator.

​
What differs between them

Only two things, and both are about rendering rather than capability:
  • Output format. Widgets on web, prose on Telegram, JSON on API and CLI, a stream on POST /api/cli.
  • Depth. Long-form analysis needs a surface that can display it.
The pipeline, the data, and the entitlement are identical everywhere. An answer does not become more correct because you asked it on the web.