One consistent event shape
Resolve venue-specific symbols, market types and identifiers before the event reaches your product.
typespread.opened
symbolBTC/USDT
schemanormalized
UmbraFeed / Market-event infrastructure
Market events,
ready for products.
UmbraFeed turns fragmented CEX, DEX, funding, price and venue data into normalized, source-attributed events for AI agents, bots, research and market products.
Machine-readableCross-venue contextTraceable sources
spread.opened
BTC / USDT
MEXC → Bybit
{"type": "spread.opened","symbol": "BTC/USDT","spread_pct": 4.67,"venues": ["MEXC", "Bybit"],"confidence": 0.92,"detected_at": "18:42:07 UTC"}
One event contract
AI agent
Trading bot
Dashboard
UmbraFeedThe normalized layer between market feeds and products.
12monitored venues
4on-chain networks
<1sevent detection
01 / What you receive
A usable event contract, not another raw feed.
Each event arrives with the fields a product needs to understand what changed, where it happened and why it matters.
Market meaning attached
Receive the route, market types, funding context and event significance together with the observation.
venuesMEXC · Bybit
market typesFutures / Spot
confidence0.92
Sources preserved by default
Keep source venues, detection time and the evidence needed to explain an event downstream.
event IDEVT-82941
detected at18:42:07 UTC
stateready
02 / Event families
Different market changes. The same language.
Start with the event families relevant to your product and expand without rebuilding the market-data layer.
SPREAD OPENED
A meaningful price difference appears across venues.
Use a normalized cross-venue observation with route, price difference and market context already attached.
Inspect the event schema →spread.openedValid event
{
"type": "spread.opened","symbol": "BTC/USDT","venues": ["MEXC", "Bybit"],"spread_pct": 4.67,"confidence": 0.92,"detected_at": "18:42:07 UTC"
}MEXC · Bybit
Futures / Spot
Ready
03 / Work with Umbra
From product fit to production.
We define the event contract around the product you are building, validate it with real market events and agree the right path to production.
Start a conversation →Define the use case
Align on users, event families, market coverage and the decisions the integration must support.
Integration brief
Validate with a focused pilot
Review real event objects, source attribution and the representation required by your product.
Working event flow
Move into production
Confirm delivery, operational expectations and the commercial model for continued access.
Production agreement
Build on the market-event layer.
Tell us what your product needs to understand about the market. We will show how UmbraFeed can deliver it as a consistent event.