Explore the code A published specification
The registry is searchable programmatically, not by scraping a page.
Agent access
Give your agent the chain.
Not a paragraph about it.
A machine-readable surface for coding agents: a published specification, installable skills, and account access that does not require a human to open a dashboard.
- OpenAPI specification
- Installable skills
- Agent account access
- Machine readable
Ethereum → Firehose → Substreams → PostgreSQL
Interactive illustration
StreamingFast
ecosystem
01 Agent access
Looks familiar?
Your agent cannot infer a schema from a documentation page written for a human.
You teach it your stack again in every new conversation.
It gets to the edge of the task and stops, because the next step needs someone to log in.
Want your own assistant to try it?
Read the specification
RUST → WEBASSEMBLYDocumentation an agent can parse, not just read.
An assistant is only as useful as the surface it can act on. The package registry publishes an OpenAPI specification, the expertise ships as installable skills rather than prompt text, and account operations are reachable without a password ever touching the agent.
Read the guideFilterMapAggregateDeliver
▧ substreams.yamlPACKAGE STRUCTURE
01 specVersion: v0.1.0
02 package:
03 name: token_transfers
04 version: v0.1.0
05
06 modules:
07 - name: map_transfers
08 kind: map
09 inputs:
10 - source: sf.ethereum.type.v2.Block
11 output:
12 type: proto:transfers.Transfers Illustrative excerpt Build a complete package ↗
What you get
Installable skills
Manifests, chain-specific decoding, SQL sinks, deployment and testing, as knowledge packs.
Agentic account access
Usage, keys and deployments, without handing over a password.
Open source packages
The agent can read what it is building on.
Works with the tools you use
Coding assistants that accept skill packs pick it up directly.
02 Agent access
How it works
FROM HISTORY TO THE CHAIN HEAD
Historical blocksNew blocks
TRANSACTIONS
TRACES & LOGS
STATE CHANGES
Rich block data. One continuous stream.
Install the skills
One command in the assistant you already use.
Point it at the registry
It searches and pulls packages on its own.
Let it ship
From manifest to deployed sink, without a browser.
Want your own assistant to try it?
Read the specification03 Agent access
What you stop owning
[01]
Re-explaining your stack in every conversation
[02]
The copy-paste between the docs and the editor
[03]
The manual step in the middle of an automated task
Agent access
Hand it to your agent, not to a developer.
Read the guide ↗Turn transactions into reliable data
Separate decoding from business logic, preserve event order and make every derived value traceable.