Agent Readiness Protocol

The description states that Agent Readiness Protocol is a self-reported open protocol for defining and verifying what AI agents need before enterprise deployment. The project was built as part of the OpenAI 2026 hackathon by one individual, Ged Ossman. It includes a readiness.yaml contract to define dependencies with verifiable criteria, and uses tools like Codex, Markdown, and YAML.

What changed: The author reports building a small, standalone protocol that aims to make enterprise AI agent rollouts more coordinated by making dependencies explicit early in the process.

Single most important open question: Is there any evidence of traction, adoption or usage beyond this hackathon submission? The description does not indicate whether the protocol has been used in real-world deployments or tested with actual enterprises.

Analysis basis: This report is based on a self-reported project description from the author. No independent verification or external data is available. All claims are treated as stated by the author, not proven facts.

The description states that Agent Readiness Protocol:

• Creates a readiness.yaml contract
• Defines what an AI agent needs from an enterprise
• Includes verifiable criteria for each dependency
• Covers integrations, authentication, data, infrastructure, stakeholders, and approval processes

It also mentions three installable skills built with OpenAI Codex:

1. Drafts the readiness contract
2. Previews rollout at a specific enterprise
3. Provides the protocol specification and dependency categories

Inference: The product appears to be a lightweight, declarative framework for specifying and validating agent readiness requirements in an enterprise context.

The description states:

• AI agents are powerful but enterprise rollouts often stall due to missing system access, SSO, data, security reviews, unclear ownership, and internal approvals.
• The goal is to have vendors and enterprises agree on readiness before deployment begins.
• It aims to solve a coordination problem, not just a technical one.

Claim: The protocol helps teams work in parallel by making dependencies explicit early.

Inference: This positions the product as a pre-deployment coordination tool for AI agent rollouts, rather than a runtime or infrastructure solution.

The description states:

• The target is enterprises deploying AI agents.
• It addresses issues like missing system access, SSO, data, security reviews, unclear ownership, and internal approvals.
• It aims to help security, IT, data, legal, and business teams work in parallel.

Inference: The ICP appears to be enterprise teams involved in AI agent deployment — particularly those managing cross-functional coordination between technical and non-technical stakeholders.

Not evidenced.

Finding: No information is provided about pricing, monetization or business model. The project is described as a hackathon submission with no indication of commercial intent or revenue streams.

The description states:

• Built using OpenAI Codex, Markdown, and YAML
• Includes three installable skills (drafting, previewing, specification)
• Next steps include adding JSON Schema, lightweight validator, reusable industry profiles, and a GitHub Action

Inference: The technical approach is declarative and tool-based. It uses open-source or low-code tools and aims to integrate with CI/CD workflows via GitHub Actions.

Not evidenced.

Finding: There is no evidence of traction, customers, usage, or adoption beyond the hackathon submission. No data on headcount, revenue, partnerships, or product usage is provided.

Not evidenced.

Finding: No mention of existing tools or competitors in the AI agent deployment or enterprise readiness space. The description does not provide context for how this compares to other solutions.

• Single founder: Only one team member (Ged Ossman) is listed.
• Hackathon project: No indication of post-hackathon development, traction, or commercial viability.
• No verification: The protocol is self-described and not independently validated.
• Unproven adoption: No evidence of real-world usage or enterprise testing.

Inference: The lack of a team, traction, or product-market fit signals high risk for commercial viability or scalability.

1. What specific enterprise use cases have you tested this protocol with?
2. Have you validated the verifiable criteria with real stakeholders in enterprises?
3. How does this differ from existing tools for defining system dependencies or readiness?
4. Is there any plan to build a community or ecosystem around this protocol?
5. What is your roadmap beyond the hackathon, and how do you intend to monetize it?