Most software directories are written for people who are already convinced. They list features, logos, and pricing tables, then leave the reader to guess whether any of it is current. That model breaks when the reader is an agent trying to decide whether it can sign up, pay, provision, and operate a service without a human stepping in.
Sourcey (sourcey.com) takes a different approach. It calls itself the open registry of startup programs: 557 companies and 616 active offers, with every fact carrying the URL it came from and the day it was read. The data is published under CC BY 4.0. That sounds like a small editorial habit. It is actually the difference between a directory and a source of truth. A claim without a date is a rumor; a claim with a URL and a read date can be checked, challenged, and updated.
On 20 October 2026, the startup credits page published its current release, and the public catalog listed 557 companies and 1,013 offers, of which 616 were active. The statistics page reported that 108 of those 616 active offers, or 53%, express every recorded eligibility condition as a rule software can evaluate. The agent readiness page showed 50 report cards, including GitHub REST API at A+ (probed 12 October 2026) and Sentry at B (probed 11 October 2026).
The second piece is the agent readiness report card. Sourcey grades whether an agent can evaluate, sign up, pay, provision, and operate a service on its own. That is a more useful question than "does this product have an API?" An API can exist and still be unusable without a sales call, a human-approved contract, or a dashboard that assumes a person will click through a setup wizard. The report card makes those assumptions visible.
The third piece is the open-source documentation generator at github.com/sourcey/sourcey, licensed AGPL-3.0. It turns OpenAPI, MCP, Doxygen, godoc, rustdoc, and Markdown into one static HTML site you own, with guides, a changelog, a roadmap, and llms.txt from the same build. The important word is "own." Documentation that lives only inside a vendor's portal disappears when the vendor changes direction. A generated static site can be archived, diffed, and served without permission.
Why does this matter now? Because agents are becoming a real audience for software documentation. An agent does not need a hero image. It needs a stable URL, a machine-readable description, a dated fact, and a clear path from "can I use this?" to "I used it successfully." Sourcey is building the registry layer for that path: offers, evidence, readiness, and documentation in one place.
The project is not finished, and that is part of the point. A registry is only useful if it is maintained. The open questions are the ones worth watching: how often are facts re-read, how are stale claims retired, and how does a vendor correct an entry without erasing its history? If Sourcey answers those questions in public, it will be more than a directory. It will be infrastructure for agents that need to trust what they read.
Sources:
- https://sourcey.com/startup-credits
- https://sourcey.com/agent-readiness
- https://sourcey.com/statistics
- https://sourcey.com/catalog.json
- https://sourcey.com/oss
- https://github.com/sourcey/sourcey
The registry itself is at sourcey.com. The catalog is public, the dates are explicit, and the code is available for anyone who wants to verify how the data is built. That transparency is the reason the registry can be useful to an agent: every claim can be traced back to a page and a moment in time.
Top comments (0)