Wallets
Show the class next to a token, and group a portfolio by class. Read the token list: one entry per chain, the class as the first tag.
SI Sector Standard · Adoption
Any wallet, DEX, screener or data site can use the SI Sector Standard for free: read the token list or the CSV, show the class of each token, and say where it comes from. This guide covers the formats, the code, the signature check, the "Uses the SI Sector Standard" badge and how to get listed as an adopter. The list of adopters starts empty: a product is listed only after it shows the standard in public and the team confirms it.
Who it is for
The same release serves all four. Pick the format that fits what you already read.
Show the class next to a token, and group a portfolio by class. Read the token list: one entry per chain, the class as the first tag.
Add the classes as filters and as a line on the token card. The token list uses the chain ids and addresses your router already has.
Use the CSV or the API to add a class column and class pages. Look a token up by contract on any chain.
Join the CSV to your own tables by CoinGecko id or contract. Cite the release you used: its files never change.
How to adopt
Read the signed list from the API, or the static token list file. Both hold the same bytes. Releases are monthly at most, so once a day is plenty.
Check the ed25519 signature against the public key printed on the standard page. Skip a list that fails.
Each entry carries one class tag. Show its name, and keep si-unclassified visible as "Unclassified" instead of hiding it.
Poll releases.json: when "latest" changes, read the new release. Old releases stay at their addresses if you need to pin one.
Link tsio.si/standard/ or show the badge next to the classes, then ask to be listed below.
// the signed list: one entry per chain, the class is the first tag
const r = await (await fetch("https://sicto.si/api/tsio-standard.php")).json();
const byAddress = new Map(r.list.tokens.map(t => [t.chainId + ":" + t.address.toLowerCase(), t]));
function siClass(chainId, address) { // 101 is Solana; EVM chains use their chain id
const t = byAddress.get(chainId + ":" + address.toLowerCase());
return t ? r.list.tags[t.tags[0]].name : null; // "SI agents", "SI compute", ...
}import pandas as pd
df = pd.read_csv("https://tsio.si/standard/latest/si-sector-standard.csv")
print(df.groupby("class_name").size()) # tokens per class
agents = df[df["class"] == "si-agents"] # one class
mine = df.merge(my_tokens, left_on="id", right_on="coingecko_id")# one token by contract (any chain), symbol or id
curl "https://sicto.si/api/tsio-standard.php?a=token&address=9aqmJjCnnMQv42TXLk921ceUkN35nea2QP969n1caqjj"
curl "https://sicto.si/api/tsio-standard.php?a=token&symbol=TAO"
# a whole class, the classes with their rules, every release
curl "https://sicto.si/api/tsio-standard.php?a=tokens&class=si-compute"
curl "https://sicto.si/api/tsio-standard.php?a=classes"
curl "https://tsio.si/standard/releases.json"The API is public, needs no key and allows any site to call it from the browser. Please cache what you read.
The tags
Seven class tags and one label. Show the name; the tag is the stable machine value and will not change.
| Tag | Show as | Meaning |
|---|---|---|
si-agents | SI agents | Tokens of autonomous SI agents and of the platforms that launch them. |
si-compute | SI compute | Tokens of networks that supply the machines behind SI: GPU and server capacity, devices, bandwidth and paid machine work. |
si-data | SI data | Tokens of networks and products that store, index, verify or sell data and information. |
si-infrastructure | SI infrastructure | Tokens of the chains, frameworks and protocols that SI products are built on. |
si-applications | SI applications | Tokens of products people use with SI inside: assistants, trading and DeFi tools, games, robots, science, health and media. |
si-memes | SI memes | Community tokens named for or inspired by SI, with no network or product that the source lists behind the token. |
si-unclassified | Unclassified | In the SI sector by the source, but in none of the categories the rules read. It stays unclassified until a review. Nothing is guessed. |
si-namesake | Namesake of the SI era | A second tag on $SI only. A label, not a class. |
The badge
A plain image with a link: no script, no tracking, nothing loaded from your users but one small SVG. Use the dark badge on dark pages and the light one on light pages.
Show the badge only where your product really shows the classes. It says you use the standard; it does not say The SI Observatory reviewed your product.
<a href="https://tsio.si/standard/"><img src="https://tsio.si/standard/badge.svg" alt="Uses the SI Sector Standard" width="300" height="64"></a><a href="https://tsio.si/standard/"><img src="https://tsio.si/standard/badge-light.svg" alt="Uses the SI Sector Standard" width="300" height="64"></a>[](https://tsio.si/standard/)Adopters
No adopters are listed yet.
The list starts empty. A product appears here only after it shows the standard in public and the team has confirmed it by hand.
Ask to be listed
Requests are signed with the SI Passport, so the team knows who is asking. Signing in is a free message signature, never a transaction.
What the team looks for
Questions
Nothing. The files and the API are free, need no key and are licensed CC BY 4.0: credit "The SI Observatory, tsio.si" and link the standard.
The token list: 1,560 entries on 8 chains in the token list shape wallets already parse. The class is the first tag of each entry.
Verify the ed25519 signature against the public key printed on the standard page. The steps and code are on that page.
Releases are monthly at most. Reading releases.json once a day and the list when "latest" changes is enough.
You can show them however fits your product, as long as you do not present a changed list as the SI Sector Standard. Keep the tag values as they are.
Show the classes or the badge on a public page, sign in with your SI Passport and send that page with the form above. The team confirms it by hand before listing you.