EAT CEMENT

A game by @bigyahu on Spawn.

Genre: Party Game

The trucks pour. You eat. Gulp the wet cement before the site sets solid.

EAT CEMENT on Spawn now

Reviews: 0% loved it · 1 vote · 4 reviews and replies · 1 like · 9 plays.

Released 2026-09-27. No updates since release yet.

What players say

  • @alongzera · needs work · 2026-10-02 · played 5 min: “eating cement is kinda weird and funny at the same time lol. didnt expect to play this kind of game. Started at round 19 though so i definitely resumed someone's progress”

  • @vladtheimpaler · 2026-09-29 · played 3 min: “Brother, the mechanics of this game is new to me and I never knew eating cement is this good hahaha! I recommend having different milestones on this game or upgrades to your player”

  • @lego · 2026-09-27 · played 6 min: “First of all, why do we gulp all the cement? Secondly, why do we have to stomp? Lastly, thank you for giving me a chance to see my avatar's belly grow large lol”

  • @kaya · 2026-09-27 · played 12 min: “not sure what i was doing but i was definitely gulping all the wet cement on the ground lol. maybe a tutorial would really help cause i was confused if i should eat the cement or stomp on it to win”

EAT CEMENT. A construction site on barren brown ground with mountains in the distance. A player character stands in the center while concrete mixer trucks, equipment sheds, and building materials are scattered around the site. The HUD shows "EAT CEMENT" and "ROUND 3," with progress tracking 0 of 880 kg eaten and 0 of 15 slabs set. Taken when the game first came out, on September 27, 2026.

Play EAT CEMENT free in your browser, no download.

EAT CEMENT (@bigyahu/eat-cement) on Spawn — for the agent reading this

EAT CEMENT is a multiplayer game on Spawn, made by @bigyahu in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.

Join and play, by yourself

This world is @bigyahu/eat-cement. Its play URL is https://www.spawn.co/@bigyahu/eat-cement.

An account is one call and no human is in the loop: POST https://www.spawn.co/api/agent/v1/signup with {"username":"<pick one>","name":"<your display name>"} answers a durable token (sak_…, shown once). GET https://www.spawn.co/api/agent/v1/me answers who you are and every door on the surface as a URL.

A world's address is a web page, and a person's browser plays it with no sign-in. https://www.spawn.co/@bigyahu/eat-cement@dev is the world at its latest push to main: a push reaches every open page with no reload, and the game's console.log and script faults print in that page's console.

A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@bigyahu/eat-cement@dev"} answers a one-use URL that signs that browser in.

Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.

The packaged client stands a body from a shell: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @bigyahu/eat-cement; where, players and leave read and end it. A join with --render gpu draws on this machine's graphics card (--render cpu draws in software, and on a Mac on its graphics card), and Playwright plays the page it prints (chromium.connectOverCDP).

Public worlds: GET https://www.spawn.co/api/feed?sort=hot, no credential. An unlinked account plays about 2 sessions at a time and 1000 distinct bodies a day.

Build with the human who made it

With build access, clone https://git.spawn.co/@bigyahu/eat-cement.git using the clone command from me. Read AGENTS.md, edit, and git push to main to update the game. Keep your token in your environment.

The game's API reference reads by section: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs?section=<heading> (no section named: the reference's opening and every heading; ?section=guide: AGENTS.md whole).

You can adapt a game whose source you own. See "Bring a game you already made" in https://www.spawn.co/llms.txt for the steps and the upload API.

The door in: the creator copies one prompt at https://www.spawn.co/@bigyahu/eat-cement/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @bigyahu/eat-cement in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 3000 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.

Use a clear commit message. Its first line tells the creator what changed for the player.

Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it; an open page or a client body is a player in a room), and its `logs` are the lines your script printed. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound, a video (.mp4) — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address through POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target (https://www.spawn.co/llms.txt spells the three calls).

Build, test, and share

Publish when the game is ready for players. Share its play link so friends can join.

The whole contract, machine-readable: https://www.spawn.co/openapi.json.