For founders: how a listing becomes visible to AI agents automatically, and which fields make it rank for the right questions.
When you submit a product on Founder.best and it goes live, the same record immediately powers your product page, its JSON-LD, the public API, the Markdown mirror, llms-full.txt and every MCP search result. Edits you make from the dashboard propagate to all of them at once. There is no “enable AI” switch - being listed is being discoverable.
| Surface | When it updates |
|---|---|
| Product page & JSON-LD | Immediately on approval or edit |
| REST API record | Immediately (edge cache refreshed on edit; otherwise ≤5 min) |
| MCP tool results | Immediately - tools query the database live |
| Markdown mirror | Immediately on edit; otherwise ≤5 min |
| llms.txt / llms-full.txt | Immediately on edit; otherwise hourly |
| Search engines & AI crawlers | On their next crawl; the sitemap lists your page |
Agents search the way people ask: “tools for X”, “something for freelancers that does Y”. The fields below are the ones search matches against and filters on, in rough order of impact.
featureList / audience in structured data. Pick the ones a customer would type.integrations and let agents recommend you for automation tasks.metrics.verified_revenue.Check your own listing the way an agent sees it.
Open https://www.founder.best/products/your-slug.md and https://www.founder.best/api/v1/products/your-slug. If the AI-ready profile reads well and the use cases / audiences are filled in, you are in good shape.
updated_at is exposed so agents can prefer fresh listings.See How it works and Pricing for the launch side of things.