Skip to main content
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: If you only need updates for a known set of wallets, Webhooks are simpler. Streams are for ingesting the full firehose of activity across chains into your own 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. Our team handles onboarding, access provisioning, and topic and schema details.

​
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.