Skip to main content

OpenA2A at IETF 127

San Francisco, November 14 to 20, 2026. We're at the IETF 127 Hackathon and meeting week with an open test suite for AI agent credentials. A test suite only proves something when it runs on code its authors didn't write, so we're looking for verifiers and issuers built by other people.

What we're doing

Our Hackathon project, Agent credential conformance: build evidence, authorization and identity, runs open conformance fixtures through verifiers we didn't write. Each fixture has a known correct answer: some must be accepted and some must be rejected. Where your verifier and our fixtures disagree, either your code has a bug or our specification is unclear, and we file the difference together the same day.

We're also implementing other drafts from their text alone and reporting where the text had to be guessed: Mission-Bound Authorization from the OAuth working group, and, as time allows, the WIMSE agent delegation chain and fixtures for AIMS.

Find us

Hackathon table: Saturday, November 14, 10:30 to 20:30, and Sunday, November 15, 9:30 to 13:30. Continental 4, Hilton San Francisco Union Square. Results are presented Sunday from 14:00.

Side meeting: Thursday, November 19, 11:30 to 12:30 Pacific, Continental 7. A hands-on hour: Hackathon results first, then participants run the fixtures through their own verifiers. Join remotely at https://ietf.webex.com/meet/sidemeetings1.

The Hackathon is free and open to everyone, but it needs a registration at https://registration.ietf.org/127/. The side meeting is open to all registered IETF 127 participants.

Join remotely

Post in the IETF Hackathon Zulip stream at any time. We check in at fixed times, all Pacific:

  • Saturday at 12:00 and 17:00
  • Sunday at 11:00

Run the kit

You need Go 1.22 or later (1.23 or later on macOS 26). The kit runs on your laptop, uploads nothing, and needs no network after the install.

bash
go install github.com/opena2a-standards/atx-conformance/cmd/atx-verify@4f70281a00163ec898e9671ba9ab023907e402b2

Point it at your verifier:

bash
atx-verify --verifier-url http://localhost:8080/

It reports, for every fixture, whether your verifier agreed with the expected result, disagreed, or couldn't read the input. Full instructions are in the repository: https://github.com/opena2a-standards/atx-conformance

Credit, and a bug bounty

Everyone who runs the fixtures is credited by name in our results, with their permission.

If you find a bug in our fixtures, kit or specification, report it as a GitHub issue on the repository. For each confirmed bug reported November 14 to 20, 2026, we donate 100 US dollars to the open-source project or nonprofit of your choice, up to 1,500 dollars in total. Confirmed means we can reproduce it, and we either fix it or agree the specification was unclear. The first person to report each bug counts.

The drafts we're working with

Contact

info@opena2a.org, or find Abdel Sy Fane at the table.

After the meeting, this page becomes our results: what we tested, with whom, and what we found.

OpenA2A is participating in IETF 127. This page is ours, not the IETF's, and doesn't imply endorsement by the IETF.