AsyncAPI channel · ThunderCore · ThunderCore WebSocket JSON-RPC event surface

/

Ethereum JSON-RPC pub/sub channel: clients call eth_subscribe over the WebSocket (subscription types per the Ethereum convention, e.g. logs for contract events — the use case the ThunderCore docs call out) and receive eth_subscription notifications.

Open source AsyncAPI → All ThunderCore channels ThunderCore provider profile
Provider: ThunderCore AsyncAPI: v3.0.0 Spec: ThunderCore WebSocket JSON-RPC event surface Operations: 1 Messages: 2

Channel address

/

Operations

send
subscribe
Open a subscription (the docs recommend WebSockets for pushing new logs as they become available).

Messages

eth_subscribe
Content-Type:
eth_subscription
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.