The Open Agentic Web Challenge, hosted by Cognizant with technology contributions from Cognizant AI Lab, MIT Lab's NANDA program, Mozilla Otari and AWS, invites developers everywhere to build the open-source building blocks of an agentic web: agents that run in the browser on the web technology that already exists, so that agents can discover and connect with other agents, and work across platforms.

Agentify a website, create a tool that helps agents find or trust each other, or a reusable component the whole community can leverage. Everything you build is open source, so the best ideas become part of the foundation everyone builds on next.

Whether you're a web developer who has never built an agent or an AI engineer who has never shipped to the browser, there's room for you here.

Get started

  1. Register for the hackathon on this page.
  2. Check out the GitHub repo and read the minimum viable specifications for a worldwide open agentic web
  3. Build your agentic website that demonstrates your idea or building blocks
  4. Submit your project on Devpost before January 11, 2027 at 16:00 UTC.

Requirements

What to Build

Entrants must create a working open agentic website built with standard open web technologies that conforms to the open agentic web specification.

What to Submit

  • Provide the URL to your (public) open agentic web site. It must contain the following:

    • a publicly accessible conforming `.json` file that describes an agent network and its capabilities

    • a `runtime` file that can run the agent network in the browser

    • an interface that allows users or agents to interact with the agent network

    • an optional interface that allows users to configure LLMs and keys to be used by the agents

    • the agent network should be able to interact with the website, optionally with other agentic websites, and/or be called by other agentic websites

  • Include a text description that should explain the features and functionality of your Project.

  • Include a video of you demonstrating your Project in a browser. The video portion of the Submission:

    • should be less than two (2) minutes. Judges are not required to watch beyond two minutes 

    • should include footage that shows the Project running in a web browser

    • must include the Entrant explaining the Project (not AI generated)

    • must be uploaded to and made publicly visible on YouTube and a link to the video must be provided on the submission form on the Hackathon Website; and

    • must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.

  • Provide one or more screenshots of your website.

  • If your project uses Mozilla Otari:

    • Provide the email on your Otari account so we can match your submission to your usage.

    • In a sentence or two, include a problem you faced when using Otari and how it could improve.


  • Optional but encouraged: Entrants who build additional tools or services while creating their Project and share them with the community may describe and link them in their Submission. These may be considered under the Potential Impact criterion.

Hackathon Sponsors

Prizes

$10,000+ in prizes
+ other prizes
First place
$5,000 in cash
1 winner

$1,500 Mozilla Otari credit, SWAG, Social promotion

Second place
$3,000 in cash
1 winner

$750 Mozilla Otari credit, SWAG, Social promotion

Third place
$2,000 in cash
1 winner

$500 Mozilla Otari credit, SWAG, social promotion

Employee prize
1 winner

$250 Mozilla Otari credit, SWAG, social promotion

Judges

Babak Hodjat

Babak Hodjat
Chief AI Officer, Cognizant

Ramesh Raskar

Ramesh Raskar
Prof. MIT Research and Founder Project NANDA

Risto Miikkulainen

Risto Miikkulainen
Prof. Computer Science, UT Austin

Judging Criteria

  • Technological Implementation
    How well is the project built, and how effectively does it use the open agentic web specification?
  • Design
    Does the project deliver a complete, coherent product experience not just a technical proof of concept?
  • Potential Impact
    Does the project make a credible, specific case for solving a real problem for a real audience and does the solution actually address it based on what's demonstrated? Does it include any tools or services the Entrant built and shared with the community?
  • Quality of the Idea
    Is this a creative, non-obvious use of an open agentic website and does the team show genuine understanding of the problem space?

Questions? Email the hackathon manager

Invite others to compete

Hackathon sponsors