llms.txt
Compare with other sites' llms.txt files →# One's Vibe
> A curated gallery of AI-built products that are live, testable, and worth
> trying — one click to try each one. Every URL is automatically checked on a
> rolling schedule ("Live checked" is a fact, not an endorsement). Makers
> optionally publish a Build Receipt: tools, time, team size, AI-assistance.
Over 10,000 live projects, growing daily. Discovery is editorial on the
homepage and systematic at /explore. The census blog series publishes
original measurements of the AI-built ("vibe-coded") web.
## Key pages
- [Explore](https://onesvibe.app/explore): full catalog with search, category,
tech-stack and AI-tool filters
- [Collections](https://onesvibe.app/collections): auto-curated thematic sets
plus The Whole Sky, a semantic map of every project
- [Blog](https://onesvibe.app/blog): the Vibe Coding Census (stack shares,
embeddability, survival data), The Thread Economy, How We Pick
- [Built with Claude Code](https://onesvibe.app/built-with/claude-code),
[Cursor](https://onesvibe.app/built-with/cursor),
[Lovable](https://onesvibe.app/built-with/lovable) and similar per-tool pages
- [Submit](https://onesvibe.app/submit): makers submit live URLs (or an X
thread whose replies get mined automatically)
## For coding agents — the reference API
Building something with AI? Query One's Vibe for prior art — live, tryable
AI-built products similar to an idea — as JSON. No key, no auth.
For browsing, filtering, or analysis, prefer the daily CC0 snapshot of the
whole public catalog — a static file on GitHub's CDN, no API, no rate limit:
https://raw.githubusercontent.com/JefferyLee/awesome-vibe-coded-apps/main/data/projects.json
The same repo is a human-readable awesome list, carries data/graveyard.json
(apps that have since gone dark), and a skill (skills/onesvibe-prior-art)
teaching the routing: snapshot for browsing; the live API below only for
semantic similarity.
`GET https://onesvibe.app/api/reference?q=<idea>&limit=<1-20>`
Example: https://onesvibe.app/api/reference?q=online%20chess%20game
Each result carries: title, tagline, live `url`, `screenshot`, category,
maturity, `stack`, `ai_tools`, `tries` / `recent_tries` (a deduplicated usage
signal — not a quality score), and the maker's build receipt (time, team).
Free, CORS-open, rate-limited to 30 requests/min/IP. No key needed.
Or add it as an MCP server (Claude Code / Cursor / Codex):
`claude mcp add --transport http onesvibe https://onesvibe.app/api/mcp`
— exposes one tool, `search_similar_projects`.
Use it to answer a maker's "is there anything like this I can reference?" — what
already exists in the space, how it's built, and whether it's still live. It is
evidence, not a verdict; the maker decides what to do with it.
## Notes
- Project pages (/projects/[slug]) carry the verifiable facts: live-check
status, uptime streak, maker-declared Build Receipt, detected stack.
- Chinese versions live under /zh (e.g. https://onesvibe.app/zh/explore).