Superteam Earn alternative: a dataset approach to Solana bounty data

Two different jobs: tracking and researching

Most searches for a Superteam Earn alternative come from two very different places. If you want to get paid for bounty work, you want the platform itself: live listings, notification pings when sponsors post, a submission flow. No dataset replaces that, and we will not pretend otherwise.

The second group has the opposite problem. Aggregator builders, analysts, and agent developers do not need another place to read listings. They need the listings as data: rows they can load, columns they can trust, and enough of the underlying API structure to build their own tooling on top. A tracker gives you a screen; this page is about the alternative that gives you a dataset.

The pack documented here is a harvest of the public Superteam Earn API: 51 card records covering 17 unique live listings, 28 full listing descriptions, and a map of 186 API routes. Below is what each approach does well, so you can pick the right one for your job.

What a live bounty tracker does well

A platform tracker, Superteam Earn included, runs a real-time feed. New listings appear as sponsors post them, deadlines tick down on the page, and notifications reach you before a submission window closes. For a builder choosing which bounty to work on this week, that freshness is the whole point, and it is exactly what a static file cannot give you.

Trackers also handle the workflow side: profiles, submission forms, sponsor communication, payouts. That machinery sits outside anything a data pack touches.

What the dataset approach gives you instead

The Superteam Earn dataset was harvested from the public API on 2026-09-04 and ships four files:

• earn-listings-cards.json, 51 card records covering 17 unique live listings (the cards API paginates, so the same listing repeats once per page; dedupe on slug). The 18 fields include rewardAmount, token, deadline in ISO 8601, status, sponsor, and the agentAccess flag.
• earn-listings-full-descriptions.json, 28 listings with the complete description HTML the cards API truncates: scope, deliverables, judging criteria. 16 of the 17 live card listings appear here too, and the other 12 had already rotated off the live feed by harvest day.
• earn-api-endpoints.txt, a map of 186 routes across 25 top-level groups: listings, comments, submissions, grants, hackathons, and more.
• earn-README.md, harvest notes: date, source, file inventory, and the documented /api/search/{title} trick.

Three things a screen cannot hand you fall out of that structure:

• A documented schema. Every column has a name, a type, and a meaning you can read once and build against. No HTML parsing, no guessing which div holds the deadline.
• An endpoint map. The 186 routes show how a production bounty platform organizes its own data: what a submission endpoint touches, what a grant feed returns. Reverse-engineering that from scratch is the slow part of building an aggregator.
• MCP queries. The dataset-mcp server loads the full files and answers read-only questions: query_dataset filters rows, get_stats returns column distributions, 100 rows per call. An agent can pull a filtered table headless, no browser and no scrape.

A real query against the cards file, listings above 5,000 USD:

query_dataset(
  "earn-bounties",
  {
    "where": [{ "column": "rewardAmount", "op": "gt", "value": 5000 }],
    "columns": ["title", "rewardAmount", "token"]
  }
)

Six rows from the September 2026 test run, two unique listings after dedupe: Create Content for Breakpoint 2026 (8,000 USDG) and Solana Summit Serbia Content Bounty (10,000 USDG). That is the shape of the data your own aggregator would ingest.

Tracker vs dataset, side by side

Read the table as two tools for two jobs, not a ranking. The tracker wins on freshness and workflow. The dataset wins anywhere you need the data as data.

Who the dataset approach fits

• Aggregator builders. The card schema doubles as a starting table design, and the endpoint map shows which routes a production platform leans on. Prototype the ingest pipeline against real rows before you wire up any live source.
• Alerting logic developers. Deadlines, statuses, and submission counters as rows let you build and test the notification half of a tracker: which listings close soonest, how fast a feed rotates. The 12 aged-out descriptions show what rotation looks like in practice.
• Market researchers. Reward distributions, the bounty-to-project split, and the 45 HUMAN_ONLY / 6 AGENT_ALLOWED agentAccess split are baselines for studying the Solana work market in September 2026.
• Agent developers. The MCP calls run headless, so an agent can filter, dedupe, and pass a clean table to the next pipeline step.

For a fuller walk through the files themselves, see the Superteam Earn data guide and the web3 bounty listings data guide.

Honest limits

• A snapshot, not a feed. Every row reflects 2026-09-04. No live endpoint, no push updates. A paid refresh of the same files is planned so you can re-pull later snapshots, but nothing here updates itself, and deadlines should always be verified against the live site.
• One board. Superteam Earn covers much of the Solana ecosystem, but a multi-platform aggregator still needs hackathon boards and grant portals as separate sources.
• Harvest-day counts. 51 card records, 17 unique live listings, 28 full descriptions: these are facts about harvest day, not totals for the platform's history.
• Duplicate rows in the raw cards file. Each listing appears once per API page, so count unique slugs before reporting any number.

Framing note: this pack is a research and tooling input. Nothing on this page predicts contest outcomes and nothing here is an income estimate.

Get the bounty dataset

Check the schema with the free 10-card sample, then take the full pack if the job fits: all 51 card records, all 28 full descriptions, the 186-route endpoint map, and the harvest README.

Checkout and download run through Getly. Source: public Superteam Earn API, harvested 2026-09-04. Personal and commercial use; no resale of the files as-is.