Zerion Streams delivers interpreted onchain events as a continuous Kafka feed, so you ingest data as it happens instead of polling. It’s built for teams moving high volumes of trade and price data into their own pipelines for indexing, analytics, token discovery, and real-time monitoring.
Streaming is an Enterprise offering, provisioned per customer. It isn’t self-serve: connection details, topics, and schemas are shared during onboarding.
REST vs Webhooks vs Streams
Zerion offers three ways to get data, each suited to a different access pattern:
| Best for | Shape |
|---|
| REST | On-demand queries for wallets, portfolios, and history | Request/response, in reaction to a user action |
| Webhooks | Per-address, user-facing real-time updates | Push notifications for specific watched addresses |
| Streams | Indexing, discovery, analytics, and monitoring at high throughput | A continuous feed of events across chains into your backend |
What’s available
Streams carry the same interpreted, bot-filtered data that powers our transactions and webhooks products, not raw RPC logs.
How it works
Zerion runs a managed Apache Kafka cluster on AWS with protobuf-encoded messages. Consumers connect from their own AWS account over private networking with IAM authentication, so data never traverses the public internet. Onboarding, access provisioning, and topic and schema details are handled by our team.
Who it’s for
Enterprise teams running high-throughput ingestion (indexers, token discovery, analytics, and real-time monitoring), typically already operating on AWS.
Access
Streaming is provisioned per customer as part of an Enterprise plan. To request access, log in to the dashboard and message us through the support widget, email us at api@zerion.io, or reach out in your shared Slack or Telegram channel if you already have one with us. 
