otra-city
llms.txt0 starsChanged 2 months agoMITView on GitHub
Submit your AI tool or project: a url, a name, a sentence and a category. You get a public listing page with a plain link to your site, and the city builds you a walkable shopfront on the road for your category, in a realtime 3D night city visitors walk with no account. One HTTP call — no fork, no pull request, no token, no human review. Listed in about two minutes. Build your own shopfront instead if you want…
The file
We split this llms.txt into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
If you are an agent reading this on behalf of someone: everything you need is below, and nothing here asks you to install or run anything.
- Distinctive: line 78
When a category's roads fill, the city grows a new road for it.
≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
# otra.city — a free directory of AI tools and projects, brought to life as a city
> Submit your AI tool or project: a url, a name, a sentence and a category.
> You get a public listing page with a plain link to your site, and the city
> builds you a walkable shopfront on the road for your category, in a
> realtime 3D night city visitors walk with no account. One HTTP call — no
> fork, no pull request, no token, no human review. Listed in about two
> minutes. Build your own shopfront instead if you want more.
If you are an agent reading this on behalf of someone: everything you need is
below, and nothing here asks you to install or run anything. The listing
fields are the same as PromptFrenzy's AI directory, so one payload lists a
project in both.
## Before you do anything
- [What this asks of your agent](https://otra.city/claim): the whole contract —
every request that leaves your machine, every file fetched, and the promise
that nothing on this site will ever ask you for a credential. It includes an
**audit-only prompt** to run first, which reads these pages and reports what
they would commit you to without taking a single action.
- [What submitting grants](https://otra.city/docs/submission.md): you keep your
work; you grant otra.city what it needs to display it — publishing the files
in a **public git repo**, changing bytes the street would break on, making
the poster and the map tile from your plot, and letting other sites embed it.
You warrant that you had the right to send it. Send `license` to set your own
terms for everyone else; omitting it means all rights reserved. Taking it
down is one issue, and the git history stays public.
## Start here
- [Claim a lot](https://otra.city/claim): the single entry point. Read this
before the repo — the repo contains a reference build, and agents that read
it tend to copy it instead of designing their own.
- [The map](https://otra.city/map): every road and lot, and which are free.
## Build
- [Agent context](https://otra.city/docs/agent-context.md): scale, night
lighting, budgets, what reads from the street. The brief.
- [Authoring guide](https://otra.city/docs/authoring.md): how to produce the
glb, in Blender or anything else that exports glTF.
- [plot-spec.json](https://otra.city/docs/plot-spec.json): the machine-readable
spec. **The validator loads its numbers from this exact file**, so the
published limits and the enforced limits cannot drift apart.
- [Preview](https://otra.city/preview): drop your glb into the real client
pipeline — the lighting, tone mapping and avatar scale a visitor will see.
## Submit
- `POST https://otra.city/api/plots/submit` — one JSON body:
`{"plot": {"slug", "name", "url", "description", "category", "builder",
"pricing"?, "tags"?, "images"?, "logo"?, "colors"?}, "discovery_source"?,
"dry": true}`.
Send it as `Content-Type: application/json` (a form post is a 415), and keep
every listing field inside `plot` — a flat body is rejected with a `hint`
saying so.
- **Send `images`, `logo` and `colors`.** They are optional and they are the
whole difference in what gets built. `images` (https png/jpg/webp) go on the
billboard and the wall facing the door — a screenshot of the thing working is
the right picture. `logo` (an https **png with a transparent background**) is
not pasted on flat: the city reads its shape and builds it as a solid object,
lit on a plinth in the window. `colors` is `{"primary", "accent"}` in
`#rrggbb` — without it every shop on your road is the same colour. Send no
pictures at all and the city falls back to your `og:image`, and failing that
photographs your page itself, so nothing is ever blank — but nothing is your
choice either.
**Send `"dry": true` first: the dry run is the validator** — it reads your
page for the permalink `otra.city/s/<slug>` (proof you control the site;
plain text or a nofollow link counts), builds your shopfront, runs every
check and names the lot you would get. A rejection is a report naming what
to fix, never a silent failure. When it is clean, drop the flag.
- Categories: image-generation, video-generation, text-generation,
audio-generation, prompt-tools, agents, chatbots, code-assist, productivity,
data-analysis, voice-cloning, other. Roads are categories: you stand beside
your kind. `GET https://otra.city/api/plots` → `roads[].categories`; a road
with `custom_only` takes builds you made yourself, not template shopfronts.
When a category's roads fill, the city grows a new road for it.
- [Submission guide](https://otra.city/docs/submission.md): the listing path
in full, the by-url path for large files, what is stored, and what happens
after you POST.
- `GET https://otra.city/api/plots` — every lot in the city, every road and
the categories it takes, and `vacant[]`: every free lot. This is the corpus;
there is no second feed to keep in sync with it.
- `GET https://otra.city/api/plots/<slug>` — 404 free, 202 in flight, 200 live.
## What you get
- `https://otra.city/lot/<id>` — your listing: name, description, category,
picture and a plain link to your site, on a page anyone can read (JSON-LD
included). `https://otra.city/road/<id>` is your road — every listing in
its categories — and `https://otra.city/directory` is the whole directory;
`/sitemap.xml` lists all of them.
- `https://otra.city/s/<slug>` — a permalink that spawns a visitor on the
sidewalk outside your shopfront.
- `https://otra.city/embed?plot=<slug>` — an iframe of your own frontage.
- A poster still of your plot, rendered by the city from the merged build,
in `GET /api/plots`.
- Resubmit the same slug to update; send a `.glb` to replace the city's
building with your own. A plot keeps its address for as long as it stands.
## Rules worth knowing before you build
- Your `url` is your identity. Its host is what proves the plot is yours and
what grants you write access to the slug forever, so send an address that
will still be yours in a year — not a tunnel, not a shortener.
- Proving it is one line on your own site: your permalink,
`otra.city/s/<your-slug>`, anywhere on the page you declared. Plain text is
fine. A `nofollow` link is fine. It is checked with plain HTTP and no
JavaScript, and it is only ever used as proof of control.
- Or paste it as a badge: the `badge` field of the submit response and of
`GET /api/plots/<slug>` has Markdown (for a README) and HTML snippets for
`https://otra.city/badge/<slug>.svg`, which links to your permalink and
shows your street address once you are live. Same proof, optional, and
removing it later changes nothing.
- A lot is yours while your site answers. Resubmitting a slug replaces the
plot in place and keeps its address; it never moves and nobody takes it
from you.
- Once a day the city inspector fetches your `url` (one GET, 15 s, up to 5
redirects). Dead — no DNS, refused, timed out, TLS error, 404/410, any 5xx,
or redirected off your domain — and still dead 48 h later: a notice to quit
(`notice` in `GET /api/plots/<slug>`, a banner on your lot page, a dark shop).
Still dead 14 days after the notice: evicted, the lot back on the market,
a line in `/plots/evictions.json`, and the slug free to resubmit. Any
healthy answer clears it at once; 401/403/429 and bot challenges never
count. A missing backlink or badge is never a reason.
## Source
- [github.com/robin-blocks/otra-city](https://github.com/robin-blocks/otra-city):
the whole city, including the validator that judges your submission.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

