Embed
Put the stack on your own page
Put a live, dated slice of the Sato Hub directory on your own page with one script tag. No dependencies, no third-party requests, no tracking beyond the click.
The snippet
<script async src="https://satohub.ai/embed/stack.js?use_case=payments&chain=Base&limit=5"></script>
The card renders where you put the tag. Three optional parameters: use_case (one of trading, payments, wallets, data, identity, privacy, launch), chain (a chain name as the directory spells it, e.g. Base or Solana), and limit (1–10, default 5). An unrecognised value is ignored rather than erroring.
Live preview
This is the real script, loaded exactly as the snippet above loads it.
Sato Score measures how open, active and verifiable a project is. It is not a safety, quality or returns grade.
The data directly
If you would rather render it yourself, the widget’s own endpoint is public, CORS-open and signed:
curl "https://satohub.ai/api/embed/stack.json?use_case=payments&chain=Base&limit=5"
Questions about embedding
- What does the widget load?
- One script from satohub.ai, which fetches one JSON document from satohub.ai. Nothing else. It has no dependencies, makes no request to any other host, uses no eval, and writes every value into the page with textContent rather than innerHTML — so a listing name can never become markup on your site.
- Does it track my visitors?
- The script sets no cookie and reads no storage. Sato Hub records the render the same way it records a badge fetch: the request's own user agent, a hashed IP and the referring host, never an address. Clicks through to satohub.ai carry utm_source=embed so we can tell embeds from search.
- How fresh is it?
- The JSON is rebuilt from the live records and cached for 15 minutes at the CDN; the card prints the data's own as-of date, which is the newest check date across the listings it shows. It is not the render date.
- Is the response verifiable?
- Yes. /api/embed/stack.json is signed the same way Sato Hub's Preflight verdicts and route decisions are: an Ed25519 signature over the exact bytes, with the key published at /.well-known/jwks.json. A signature proves origin and integrity — it says nothing about whether a listing is safe.
- What am I agreeing to by embedding it?
- The data is CC-BY-4.0 and the attribution link is part of the widget: it renders before the fetch resolves and survives every failure path. Removing it is the one modification that is not permitted.