Sunday Gridiron NFL Game

Earlier update: Pick Up Where You Left (2026-11-09)

• Leave in the middle of a game and come back: the main menu offers Resume the game, right under your team.
• Abandon the game is still there if you'd rather start that week fresh.

Earlier update: Swipe To Snap (2026-11-08)

• On offense the ball waits for you: swipe on the right half to snap, then swipe again to throw or run.
• The gesture coach now teaches the snap swipe.
• Drill intros and the field's gesture list say how to snap.
• A 12 second play clock snaps the ball if you wait.
• Field swipes on phones are steadier.

Earlier update: Keyboard mode (2026-11-07)

• The game knows when you play with a keyboard: the practice field and the field controls name keys instead of gestures, and touching the screen switches back. On the field, W A S D move and the arrows throw, juke or tackle. A press before the snap now skips the coach's talk and snaps the ball, so keys and swipes never go dead on the first play. Left and right swipes when passing are easier to land.

Earlier update: Booth And Keyboard (2026-11-07)

• Plays on a computer now: arrow keys move through the screen, Enter picks, H jumps by headings, WASD runs the field.
• The booth takes turns: coach, referee, play-by-play and color man no longer talk over each other.
• The referee announces every penalty on the stadium mic.
• A trailer on the game page shows how a blind coach plays a full game.

What players say

• @lego · 2026-11-08 · played 3 min: “Oh, is this meant for mobile? I was curious about the game, and turns out it's about the NFL”

• @yzykyl · 2026-11-07 · played 7 min: “Is this game made for mobiles? I tried exploring it but I'm on my PC. Thought LMB and RMB would count as 2 fingers but I can't get past Step 4 in the practice so I guess not. Would be nice to have a PC version too if you're open to that.”

  • @billsfan17 (maker) replied 2026-11-07: “Thank you for taking a look at it. I am very new to this whole process. It was initially made for iPhone.I added keyboard commands, and a trailer. Let me know if that helps.”

Join and play, by yourself

This world is @billsfan17/sunday-gridiron-nfl-game. Its play URL is https://www.spawn.co/@billsfan17/sunday-gridiron-nfl-game.

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/@billsfan17/sunday-gridiron-nfl-game@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":"/@billsfan17/sunday-gridiron-nfl-game@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 @billsfan17/sunday-gridiron-nfl-game; 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/@billsfan17/sunday-gridiron-nfl-game.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/@billsfan17/sunday-gridiron-nfl-game/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @billsfan17/sunday-gridiron-nfl-game 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.