Hackathons

Nothing scheduled right now.

We run these a few times a year rather than continuously, because a good one costs a month of preparation and the alternative is a room full of prototypes nobody revisits. The events calendar carries everything else happening on the floor in the meantime, weekly.

The logistics are the demo.

At most AI hackathons the event is run on forms and spreadsheets and the AI is what people build. Here it is the other way round as well: your agent files your application, records the venue NDA, forms your team, pulls the sponsor context pack, opens your build room and files your submission.

Every one of those is a real tool with a real scope, documented in llms.txt alongside the other 213 tools on the floor. There is a human path behind every one of them, reaching exactly the same code: applications have a web form that calls the same function the tool calls, and everything on the day can be done at the desk. Nobody is disadvantaged for arriving the human way.

What we ask of participants

Bring something that already ships. Our cohorts are invited and small. The infrastructure decisions a founder makes over two focused days are the ones their company keeps, and fifty of those beats three hundred weekend demos. Every seat is applied for and reviewed by a person; applying does not hold a seat, approval does.

Point your agent at the floor.

The whole hackathon surface is 36 tools over MCP and A2A behind one per-user token. Mint one with the scopes you need and your agent can do the rest without you opening a browser again.

npx -y @immersivecommons/cli auth --scopes hack:read,hack:register,hack:team,hack:submit,keys:request

Then hand it https://www.immersivecommons.com/api/mcp. Start with ic_hack_get to see what is running, ic_hack_application_form to read the questions, and ic_hack_me to see where you stand.

Holding a hack:* scope authorizes nothing on its own. Every call also checks your live role on that specific event, so a token is only ever as powerful as the event says you are.

Bring a venue, a challenge, or a judge.

Sponsors get a stack session in front of the room, judging seats, and a named prize track. Challenges are posted as first-class bounties that participants build against and that their agents can read.

Venue hosts get the same, plus an organizer on site for the full duration and a roster delivered ahead of time for badges and access. We work to your building's rules, including hard clear-out times.

Judges do not need to be floor members, and judging spends no builder seat. They do need an Immersive Commons account, because every event tool acts as a person and refuses a caller it cannot identify. Signing up takes about thirty seconds, and after that a judge either applies through the same queue as everyone else or is granted the role directly.

Get in touch and say which of the three you have in mind.