Public API
A free, keyless, read-only JSON API over the SmartNETWORK directory: 32,654 projects across 471 blockchains. No authentication required - just attribute links to smartnetwork.cc when you build on it.
GET /api/v1/projects
Returns projects with name, chain, category, description, website, logo URL, tags and canonical slug.
Pick one of chain, category or tag as the primary
filter, then narrow further. Called without a filter it returns the directory
summary (totals + chain list) instead of a project listing.
| Parameter | Description |
|---|---|
chain | Chain id, e.g. ethereum, solana, bnb-smart-chain |
category | Category slug, e.g. defi, gaming, nft |
tag | Tag slug, e.g. dex, staking, rwa |
name | Case-insensitive substring match on project name |
slug | Exact project slug — resolves a /project/ URL 1:1 |
limit | Page size, default 100, max 1000 |
offset | Pagination offset |
Examples
GET /api/v1/projects?chain=ethereum&limit=5
GET /api/v1/projects?category=defi&limit=10
GET /api/v1/projects?tag=liquid-staking
GET /api/v1/projects?chain=solana&name=jup
GET /api/v1/projects?chain=ethereum&slug=uniswap
GET /api/stats
Community voting data. With id=Name|chain it returns that project's
likes, dislikes, dead reports and per-period counts. With period=day|week|month|year|total
it returns the top-voted projects for the period.
GET /api/stats?id=Uniswap|ethereum
GET /api/stats?period=week
Embeddable Widget
Show a live "top projects" card for any chain on your site - 471 chains supported,
one tiny iframe, automatic attribution link. Optional &theme=dark.
<iframe
src="https://smartnetwork.cc/widget/top.html?chain=ethereum"
width="380" height="330" loading="lazy"
style="border:0;border-radius:12px"
title="Top projects on Ethereum - SmartNETWORK>
</iframe>
Preview: /widget/top.html?chain=ethereum
Notes
- All responses are JSON with permissive CORS (
Access-Control-Allow-Origin: *) — works from the browser. - Chain, category and tag values are URL slugs (lowercase, dashes), the same ids used across the site's URLs.
- Be reasonable: cache responses on your side; heavy abuse gets rate-limited.
- Data updates as the directory grows — treat
totalas authoritative, not hardcoded counts.