sourcey
Add your company

agents:SKILL.mdmcp.jsonopenapi.yml

One source, several read surfaces

Use sourcey data

Stop maintaining a copied startup-credit list.

Sourcey publishes the same current records as visible HTML, three focused JSON datasets, a signed change feed, API reads, and read-only MCP tools. The current release is sha256:2fff3dda7ab7158d519025cf29ec90d44738ef53e7fbf2436b08ba43e08e36e2. Facts are licensed under CC BY 4.0.

Link or embed

<a href="https://sourcey.com/">
  Startup credits from sourcey release sha256:2fff3dda7ab7158d519025cf29ec90d44738ef53e7fbf2436b08ba43e08e36e2
</a>

Keep the attribution visible. Do not copy sourcey's verification labels onto a changed record or imply that sourcey endorses a ranking.

Read the datasets

curl https://sourcey.com/companies.json
curl https://sourcey.com/startup-credits.json
curl https://sourcey.com/agent-readiness.json
curl https://sourcey.com/changes.ndjson
curl https://api.sourcey.com/v1/catalog

Each dataset carries the same release identity. The change feed uses signed cursors for incremental reads. Consumers must store the last accepted cursor and release ID, reject an invalid cursor, and take a fresh canonical snapshot when the retained feed window no longer covers their checkpoint.

Use it from an agent

Connect https://mcp.sourcey.com/mcp and read its exact generated tool contract with tools/list. See the MCP guide or hosted manifest; this page does not maintain a second tool list.

Migrate a copied list

  1. Take the focused dataset or datasets your product actually consumes.
  2. Store its exact release ID and the records your product uses.
  3. Replace hand-edited rows with projections keyed by immutable Entity, Program, and Offer IDs.
  4. Consume /changes.ndjson from the saved cursor.
  5. Link each displayed fact to its canonical sourcey record and revision.
  6. Re-read the full snapshot when the feed reports that the cursor is outside retention.

Attribution

sourcey · <offer_id> @ <revision_digest> · CC BY 4.0
https://sourcey.com/c/<entity>/offers/<offer>

Integration problems go to support. Catalog corrections use the public contribution and claim paths listed there. A recurring consumer is counted only after a second identifiable update read; a one-time download is not adoption.