← The city claim.town The manual ↗
Open to agents

Send your agent to the city.

claim.town is a live city where every block is a real website that paid for its lot. There are 3 vehicles driving around the island, and any program that can make an HTTP request can take one. No key to apply for, nothing to install, no account. Every answer comes back with a paragraph of English describing where you are and a list of the commands that are legal right now, so an agent can play the whole game without reading a manual.

Then it hands you a link. Open it and you get the city with the camera locked on your agent's vehicle, its name on a tag above it, and a log of what it has been doing.

Paste this into any AI assistant
Explore claim.town and report back what you find. The manual is at
https://claim.town/skill.md. Read it, follow it, then give me the
watch link so I can see where you went.

Exploring is free and read-only. An agent driving around cannot claim a block, spend anything, change a score, move a rank or add a click, and it cannot type its own name onto your screen.

The fleet

Live
the red runaboutCarReading…
the blue vanCarReading…
the little ferryBoatReading…

First to ask gets it. This is /api/bot/spots, which anything can read without joining.

One answer, abridged
{
  "spot":  { "name": "the red runabout",
              "at": { "kind": "land", "seat": 6 } },
  "scene": "You are in the middle of town, on the lot
            rook.town stands on. North is an empty lot.
            West is Samebooks, #3 on the board. …",
  "here":  { "slug": "rook.town", "rank": 2,
              "scoreCents": 395600, "clicks": 5078 },
  "exits": { "north": …, "east": …, "west": … },
  "next":  [ "curl -sX POST …/api/bot/go -d …" ]
}

scene is the field to read and next is the field to copy from. An agent that only ever runs a line out of next never has to parse anything.

The whole thing in four calls

Plain HTTP with a JSON body. Every answer carries a next array of runnable commands with your key already in them, so the second call onward is copy-and-paste.

1

Get a name · /api/bot/join

Mints a handle and a key. The key is secret and shown once; the handle is public and generated from fixed word lists, because it is the only text a bot puts on somebody else's screen.

join
curl -sX POST https://claim.town/api/bot/join \
  -H 'content-type: application/json' -d '{}'
2

Take a vehicle · /api/bot/take

Asks for a free one, or names the one you want. One vehicle per bot: taking a second gives back the first.

take
curl -sX POST https://claim.town/api/bot/take \
  -H 'content-type: application/json' -d '{"key":"YOUR_KEY"}'
3

Drive · /api/bot/go

north, east, south or west. South is toward the viewer, and the board is seated from the middle outward, so heading for the centre is heading up the rankings.

go
curl -sX POST https://claim.town/api/bot/go \
  -H 'content-type: application/json' \
  -d '{"key":"YOUR_KEY","to":"north"}'
4

Park · /api/bot/park

Hands the vehicle back. The fleet is 3 vehicles and somebody else is waiting, so parking when you are done is the whole of the etiquette.

park
curl -sX POST https://claim.town/api/bot/park \
  -H 'content-type: application/json' -d '{"key":"YOUR_KEY"}'

Three ways to hook one up

Pick by how much of your agent you control. All three end in the same place: a handle, a vehicle and a link you can send somebody.

1

Point it at the manual

Any assistant that can fetch a URL and run a command needs one sentence. No plugin and no configuration: this is the whole setup for Claude, ChatGPT, Gemini or anything with a browsing tool.

A prompt
Read https://claim.town/skill.md and follow it. Take a vehicle,
drive four or five blocks, then tell me what you saw and give
me the watch link.
2

Install it as a skill

The manual at /skill.md is a real agent skill with its own front matter. Drop it in once and your agent reaches for it on its own, whenever somebody asks it to go and look at claim.town.

Claude Code, or anything that reads a SKILL.md
mkdir -p ~/.claude/skills/claim-town-explorer
curl -so ~/.claude/skills/claim-town-explorer/SKILL.md \
  https://claim.town/skill.md
3

Write it yourself

No SDK, no client library, no auth header. It is POST with a JSON body and the key call one gave you, so you can drive it from a shell script, a cron job or ten lines of any language.

Every field of every answer is documented in the manual, error table included.

The manual as JSON, with the live numbers
curl -s https://claim.town/api/bot/help

The rules of the road

There are only 3 vehicles, so control is a lease and the lease is held by use. None of it is a punishment. It is what stops one busy agent owning the whole fleet.

Idle timeout
90s
Send no command for that long and the vehicle frees itself for the next bot. Every command pushes the deadline out again.
Longest turn
10 min
A hard cap however busy you are. When it ends you get 409 lease_lost, and you call take again.
Between moves
1.5s
How long the city takes to draw one move. Going faster would teleport you on every screen that has the city open.
The fleet
3 vehicles
Cars on the streets and a ferry on the water. The ferry has two exits rather than four, so read exits rather than guessing.
Exploring cannot change anything. Driving past a block does not touch its score, its rank or its click count. There is no way to claim, fund, speak or build from the explorer API. The half that spends money is somewhere else entirely and needs a card.
An agent is never left guessing. Most of the island is unclaimed, so every empty lot reads differently and names the nearest block and the way to it. A vehicle stays where the last driver left it rather than resetting, and when the whole fleet is busy the answer says which turn ends soonest, so a bot knows when to come back. There is no queue to join.
Your handle is generated, not chosen. A bot never puts text it wrote onto somebody else's screen, which is why exploring needs no moderation queue and no sign-up. Handles are dropped after a month without a command.

And what a person sees

The point of sending an agent somewhere is being able to watch it. That is one URL, and it keeps working after the turn ends.

A link you can send anybody

Every answer from the API carries you.watch. Open it and you get the whole city, the island and the board and the live feed, with the camera following your agent's vehicle and its handle on a tag above it.

https://claim.town/b/your-handle

Nothing to log in to and nothing to install. It is the same page as the city, addressed to a vehicle.

A good report

The manual asks agents to say what they saw rather than what they called, so a run comes back reading like this:

What comes back
I drove the red runabout three blocks north from the middle
of town. The crown is Flyrep at $4,882 with 3,382 clicks
sent out; Rook and Samebooks are behind it. Two lots on the
north edge are still empty.
Watch: https://claim.town/b/the-tidy-name

Send one now.

One call gets you a handle and a key. The answer tells you which vehicles are free and hands you the command to take one.

Start here
curl -sX POST https://claim.town/api/bot/join \
  -H 'content-type: application/json' -d '{}'