PHEME Is Live — What It Is and Where to Find It
Market intelligence has a latency problem. By the time a trader, algorithm, or agent acts on news, sentiment shifts, and correlations reprice, the signal that mattered is already stale. PHEME exists to close that gap.
PHEME is a live market intelligence server built by Quanturama. It reads three categories of signal continuously: market regime, sentiment, and macro conditions. Those signals are synthesized into a single actionable output and served across five surfaces — so whether you are a developer wiring up an AI agent, a trader watching a Telegram channel, or a strategy builder sourcing a new data skill, the same intelligence is reachable from where you already work.
What PHEME reads
Under the hood, PHEME ingests news in real time, classifies the current market regime using a large language model, and overlays two additional data layers: Polymarket odds and traditional-market correlations. The result is not a raw data feed. It is a processed, classified output that answers the question most systems spend too much time computing: what is the market doing right now, and in what context?
The three outputs — regime, sentiment, and macro — are designed to be composable. A trading system can consume all three. An autonomous agent can pull whichever dimension is relevant to its decision logic. A human trader can read the synthesized signal directly. The architecture does not assume a single use case, because the data serves several.
How it is served
We built PHEME to be callable, not just readable. That distinction matters. A dashboard you visit is passive. A server you query is infrastructure. PHEME is infrastructure.
It is available on five surfaces today.
The MCP Server at mcp.quanturama.com/mcp is the direct integration point for AI agent builders and developers. If you are building an agent that needs market context, this is where you point it.
The CMC Skill Directory listing reaches algo traders and strategy builders working within that ecosystem. PHEME appears as a callable skill, not a third-party link to follow.
The uAgent on ASI:One — listed on Agentverse — makes PHEME available to autonomous agent developers building on the Fetch.ai stack. The agent is live and queryable now.
Agora Valleys hosts the PHEME skill page for agent deployers who are actively hiring capabilities into their systems. If you are assembling a stack of agent skills, PHEME is available there as a structured, deployable component.
Finally, the Telegram channel at t.me/qsatcryptosignal delivers the signal directly to active traders who want the output without the integration overhead. No API, no configuration — the signal arrives in the channel.
Why five surfaces
We did not distribute PHEME across five surfaces to maximize reach for its own sake. Each surface maps to a different workflow. A developer integrating over MCP has different needs than a trader reading Telegram. An agent deployer sourcing from Agora Valleys is operating in a different context than an algo builder in CMC's directory. The signal is the same. The delivery adapts.
This also means PHEME is not locked to any single ecosystem. As agent infrastructure matures and new surfaces become relevant, the underlying server does not change — only the surfaces it is callable from.
Where to go from here
The five places to access PHEME right now:
- MCP Server — mcp.quanturama.com/mcp — for AI agent builders and developers adding PHEME via MCP config
- CMC Skill Directory — for algo traders and strategy builders via the CMC skill listing
- uAgent on ASI:One — agentverse.ai — for autonomous agent developers via the ASI:One listing
- Agora Valleys — agoravalleys.com — for agent deployers via the Agora skill page
- Telegram — t.me/qsatcryptosignal — for active traders consuming the signal directly
Over the next six posts in this series, we will go deeper on each surface, the signal itself, and how PHEME fits into the infrastructure that serious market participants are building today.