Sato Hub
Open data

Onchain Agent Datasets

Download citable data on the onchain agent stack. No key, no signup.

Get the dataHow to cite
  • Listings487
  • Chains28
  • LicenceCC-BY-4.0
  • As of2026-10-24

Daily · since 2026-06-11

CC-BY-4.0

Agent Index

One row per framework, MCP server, wallet, payment rail, data tool or live agent.

487 listings

across 28 chains · as of

JSONCSVNDJSON
Schema & sampleShowHide

One row per listed project — frameworks, MCP servers, wallets and key management, payment rails, trading venues, data tools and live agents — with its category, chains, standards, interfaces, declared deployment and integration options, a liveness signal derived from observed repository activity, and a Sato Score (0–100) for how open, active and verifiable the project is. Catalog fields plus the current Sato Score; score history, provenance and commercial fields are not part of the free export. The score's components and inputs are in the Sato Score Inputs file.

Fields · 40

  • slug
  • name
  • category
  • subcategory
  • entity_class
  • resource_type
  • interfaces
  • standards
  • use_cases
  • description_short
  • website_url
  • github_url
  • docs_url
  • chains_supported
  • tags
  • status
  • open_source_status
  • trust_score
  • trust_tier
  • provisional
  • liveness
  • last_activity_at
  • github_stars
  • verified_install
  • verification_status
  • creator_name
  • deployment_options
  • supported_integrations
  • observed_success_pct
  • observed_days
  • observed_window_start
  • install_verified_at
  • deploy_spec
  • install
  • custody_key_access
  • custody_key_egress
  • custody_fund_action_count
  • custody_as_of
  • date_added
  • detail_url

Sample · 5 of 40 fields

namecategorychains_supportedtrust_scoreliveness
Coinbase AgentKitDeveloper ToolBase, Ethereum, Multichain91Active
HyperliquidTrading ToolMultichain, Hyperliquid77Recent
ElizaOSAgent FrameworkSolana, Ethereum, Base, Multichain87Active
JupiterTrading ToolSolana77Recent
Model Context Protocol (MCP)Developer ToolUnknown87Active

Filter with ?category= · ?chain= · ?standard= · ?use_case= · ?integration= · ?deploys_as= · ?since=YYYY-MM-DD (just the listings added or changed since that date)

  • Attribution is required: data by satohub.ai, with the date you read it.
  • A Sato Score measures how open, active and verifiable a project is. It is not a safety, quality or returns grade.
  • A null value means unknown. It never means zero.

Coverage and citation · Browse the directory

Need history or bulk by date? Platform & Data · x402 →

Weekly · since 2026-08-31

CC-BY-4.0

Agent Economy

One row per registry, chain and step, for the current week.

240 rows

week of 2026-W43

JSONCSVNDJSON
Schema & sampleShowHide

One row per (venue, chain, lifecycle stage, week), read from public chain state and public catalogues without a paid provider. Covers ERC-8004 identity registrations, Virtuals launches and graduations, x402 endpoints and facilitators, ERC-4337 and ERC-7715 account infrastructure, and staked-service networks. Every row carries its unit, its method, an evidence tier and a sample size. The free export is the current week; the weekly series stays on the site and behind the MCP server.

Fields · 23

  • venue
  • chain
  • stage
  • week
  • week_start
  • platform_host
  • belongs_to_slug
  • value
  • unit
  • method
  • evidence_tier
  • evidence_tier_meaning
  • sample_size
  • denominator
  • window_days
  • covered_days
  • publishable_rate
  • caveat
  • contract
  • stale_contract
  • as_of
  • venue_url
  • trend_8w

Sample · 5 of 23 fields

venuechainstagevalueunit
erc4337_accountsArbitrumdeployed534smart account deployed in the sampled blocks — TOTAL DEPLOYMENTS INCLUDING HUMANS, not agents
erc4337_accountsArbitrumdeployed1,192smart account deployed in the sampled blocks — TOTAL DEPLOYMENTS INCLUDING HUMANS, not agents
erc4337_accountsArbitrumintersected0sampled smart account that ALSO holds an ERC-8004 agent id or settles x402
erc4337_accountsArbitrumdeployed7smart account deployed in the sampled blocks — TOTAL DEPLOYMENTS INCLUDING HUMANS, not agents
erc4337_accountsArbitrumdeployed8smart account deployed in the sampled blocks — TOTAL DEPLOYMENTS INCLUDING HUMANS, not agents

Filter with ?venue= · ?chain= · ?stage= · ?slug=

  • Never sum rows across venues, chains or lifecycle stages — they count different objects.
  • Every figure names its stage, its method and its evidence tier; quoting one without them misrepresents it.
  • A null value means unknown. It never means zero.
  • Rates computed on a sample below 20 are carried for completeness and should not be quoted as findings.

Coverage and citation · Agent economy

Need history or bulk by date? Platform & Data · x402 →

Weekly · since 2026-09-02

CC-BY-4.0

Skill Disclosures

One row per crypto agent skill, with what it declares and does.

565 skills

as of 2026-10-19

JSONCSVNDJSON
Schema & sampleShowHide

One row per skill collected from public skill registries, with a static disclosure derived from the skill's own files: which hosts it contacts, whether it requests credentials, whether it generates or handles keys, whether it reaches a shell, and which environment variables it declares. A disclosure describes what a skill declares and does. It is not a safety verdict, and a registry's own scan status is attributed to that registry.

Fields · 15

  • id
  • name
  • description
  • registry
  • canonical_url
  • installs
  • stars
  • disclosure_flags
  • hosts_contacted
  • declared_env
  • registry_scan
  • belongs_to_slug
  • skill_md_sha256
  • as_of
  • disclosure_note

Sample · 4 of 15 fields

nameregistrydisclosure_flagsas_of
microsoft-foundryskillsshexecutes_fetched_code2026-10-19T16:45:58.027+00:00
azure-aigatewayskillsshnone2026-10-19T16:45:58.027+00:00
azure-enterprise-infra-plannerskillsshnone2026-10-19T16:45:58.027+00:00
entra-agent-idskillsshnone2026-10-19T16:45:58.027+00:00
solana-devskillsshpipes_remote_to_shell, generates_or_handles_keys2026-10-19T16:45:58.027+00:00
  • A disclosure describes what a skill declares and does. It is never a claim that the skill is safe.
  • A registry's scan status belongs to that registry, not to Sato Hub.

Coverage and citation · Browse skills

Need history or bulk by date? Platform & Data · x402 →

Quickstart

Attribution: data by satohub.ai
Terminal
$ curl -s https://satohub.ai/api/export/index.json | jq '.resources[0]'

Open slices

On Hugging Face

On Hugging FaceNeither Hugging Face dataset contains Sato Scores, score history, install specs or Sato Check evidence.

Onchain Agent Builder Bench

CC-BY-4.0

Multiple-choice questions on building onchain AI agents: stack selection, protocol facts (ERC-8004, x402, ERC-4337, MCP, A2A), reading what a package does with a key, glossary and scope. The held-out test split is not published, only its hash. Ships lm-eval-harness and Inspect AI task files.

Version
v1.0
Released
2026-10-03
Open on Hugging Face

Sato MCP Tool-Calling

CC-BY-4.0

Synthetic conversations in which an assistant uses Sato Hub's MCP tools correctly, with a share that shows when not to call Sato Hub at all. OpenAI-messages, Hermes and xlam formats.

Version
v1.0
Released
2026-10-03
Open on Hugging Face

The historic record

Dated facts and history

Every day or week, we read the public sources behind onchain agents: agent identity registries, x402 and other payment listings, MCP and skill registries, package downloads, chain and contract facts, and public blocklists. We keep a dated copy of each read, so we can say what was true on a given day, not just today. When two sources disagree, we show both, each with its own method, and never add them together.

  • NumbersWhich figure to trust: each page shows every source's number, its date and how it was counted.
  • MethodsThe rules behind the numbers, with what each one cannot see.
  • x402 facilitatorsWhich facilitator supports which chain and payment scheme, checked every day.
  • Chain cardsPer chain: its registry entry, the USDC address Circle lists, ERC-8004 registries, public RPC support and x402 facilitators, each with its source.
  • Fact lookups over MCPAgents can ask for a chain card, a contract's facts, an SDK's lineage or the x402 facilitators for a chain, and get one dated answer with its source.
  • Sources and creditsEvery outside source we publish from, with its terms and the day we last read it.

Other files

Reference

QuestionsShowHide

Questions this page answers

Is there an open dataset of onchain AI agent tools?
Yes. The Onchain Agents Index is a free CC-BY-4.0 dataset of the projects onchain AI agents are built from — frameworks, MCP servers, wallets, payment rails, data tools and live agents — rebuilt daily from public evidence and served as JSON, CSV and NDJSON at satohub.ai/api/export/index.json. No key and no signup.
How do I cite Sato Hub data?
Each dataset page carries a plain-text, APA and BibTeX citation with both the date the data was refreshed and the date you read it. The short form is: Sato Hub. <dataset>. https://satohub.ai/datasets/<slug>. Accessed YYYY-MM-DD. A figure from this site is only true of the day it was read, so the date belongs in the citation.
What licence is the data under, and can I use it commercially?
CC-BY-4.0, including commercial use, with attribution: data by satohub.ai. That covers the catalog exports, the current week of agent-economy measurements, the skill disclosures and the score inputs. It does not cover the history behind them: the full score history and the weekly agent-economy series are sold per call over x402 under an own-use licence with no redistribution, and as a monthly archive under CC-BY-NC-4.0. The licence table is on the pricing page at satohub.ai/pricing.
How often is the data updated?
The directory index and the score inputs are rebuilt daily. The agent-economy measurements and the skill disclosures are collected weekly. Each dataset page states its own cadence and the date its series begins.
What is not in these datasets?
Score history and commercial fields stay on the site. The score's components and inputs are free, in the Score Inputs file. Nothing about who reads or queries Sato Hub is published anywhere: these datasets describe the onchain agent stack, not this site's traffic.
Cite this pageShowHide

Archived snapshot DOI: 10.5281/zenodo.22814238

Cite the dataset page with the date you read it. The pattern:

Sato Hub. <dataset>. https://satohub.ai/datasets/<slug>. Accessed YYYY-MM-DD.

Worked example, in three formats:

Sato Hub. "Onchain Agents Index." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/datasets/onchain-agents-index https://doi.org/10.5281/zenodo.22814238

Sato Hub. (2026, October 24). Onchain Agents Index [Data set]. Sato Hub. Retrieved October 24, 2026, from https://satohub.ai/datasets/onchain-agents-index https://doi.org/10.5281/zenodo.22814238

@misc{satohub-datasets-onchain-agents-index-2026-10-24,
  title        = {Onchain Agents Index},
  author       = {{Sato Hub}},
  year         = {2026},
  month        = {10},
  howpublished = {\url{https://satohub.ai/datasets/onchain-agents-index}},
  urldate      = {2026-10-24},
  note         = {Data set, last updated 2026-10-24. Licensed CC-BY-4.0.},
  doi          = {10.5281/zenodo.22814238}
}

Each dataset page carries its own copy-paste block. Licence: CC-BY-4.0, attribution data by satohub.ai.