Zerion Streams Now Live: Real-time Onchain Data Over Kafka
Zerion Streams are managed Apache Kafka feeds that continuously deliver real-time onchain transactions and prices into your backend.
Polling thousands of wallet addresses works fine. But as your user base grows, you start to hit rate limits while data becomes stale.
Zerion Streams are managed Apache Kafka feeds that continuously deliver interpreted EVM and Solana transactions and prices into your backend as they happen.
Zerion API now offers the complete wallet data stack:
- REST API endpoints: poll with wallet addresses and get fully interpreted responses,
- Webhooks: subscribe to specific wallet events,
- Streams: receive a continuous Kafka feed of events.
Interpreted onchain data
Many providers sell price feeds and raw blockchain data. Zerion Streams deliver interpreted data.
Here is an example of what Zerion Streams’ protobuf message decodes to for a DEX swap on Polygon:
Every event carries the same interpreted, bot-filtered data behind other wallet API endpoints:
- EVM and Solana across one schema
- Fully enriched with token metadata, prices, transaction types, and app labels
- Delivered in real-time, at the speed of blockchain
What it solves
Zerion Streams tackle the issues with scaling REST API polling beyond a certain point:
- Rate limit pressure
- Stale data
- Increasing infrastructure costs
Streams are made for teams running high-throughput ingestion at scale. This includes token discovery, analytics, and real-time monitoring.
How it works
Zerion Streams run on a managed Apache Kafka cluster on AWS with protobuf-encoded messages.
You consume from your own AWS account over private networking with IAM auth, so data never crosses the public internet. Zerion handles the cluster, onboarding, access, and schemas.
Streaming is an Enterprise offering, provisioned per customer.
Get access
Book a demo with our team. We'll walk through the available streams, architecture, and onboarding for your setup.
FAQ
What is Zerion Streams?
Zerion Streams is a managed Apache Kafka feed of interpreted onchain events. It pushes trades and token prices into your backend in real time, so you stop polling for them. It's aimed at teams moving a lot of onchain data into their own pipelines for indexing, token discovery, analytics, and monitoring.
How is Streams different from the REST API and Webhooks?
They all serve the same interpreted Zerion data, just in different ways. The REST API answers on-demand queries about wallets, portfolios, and history. Webhooks push updates for specific addresses, which works well for user-facing alerts. Streams sends a continuous feed of events across chains into your backend, which is the right fit when you're ingesting at high throughput.
What onchain data is available on Streams?
EVM trade actions across supported EVM chains, Solana trade actions, and token price events. Every event carries the same interpreted, spam-filtered data behind Zerion API endpoints and webhooks. Data comes with token metadata, prices, transaction types, and app labels already attached.
Which blockchains do Zerion Streams support?
Solana and the supported EVM chains. They arrive in one schema, so you don't have to build a separate ingestion path for each chain.
Do I have to run my own Kafka cluster?
No. Zerion runs the managed Apache Kafka cluster on AWS and takes care of onboarding, access, and schemas. You just consume the data feed.
How do I connect, and is the data secure?
You consume from your own AWS account over private networking with IAM authentication. The data never crosses the public internet. Messages are protobuf-encoded, and we share connection details during onboarding.
How much does Zerion Streams cost?
Streaming is an Enterprise offering, and we provision and price it per customer based on your chains, event types, and expected volume. Get in touch, and we'll put together access for your use case.