Product Brief

Agentic Readiness Module

The trust layer for AI-initiated commerce

A proposed seventh module for Identity Advantage that validates whether a business can be transacted with by AI agents, and issues a public "Agentic Ready" status on the Identity Record.

CompanyIdentityRecord
AuthorClaude (CTO execution partner)
StatusProposed — awaiting founder review
PriorityHigh — 12-18 month competitive window
DateApril 2026
01

Why This Matters Now

OpenAI launched its Agentic Commerce Protocol in September 2025. Google launched Agent Payments Protocol the same month. The rails for AI-executed transactions are live. AI agents are moving from recommending businesses to transacting with them: booking appointments, requesting quotes, processing payments.

The missing layer is trust. No system currently validates whether a local business is safe and ready for an AI agent to transact with. The business that is Agentic Ready gets the booking. The one that is not gets skipped entirely.

This is the next evolution of the eligibility thesis: from "eligible for recommendation" to "eligible for transaction."

The window to own this narrative is 12 to 18 months before Yext or a well-funded GEO startup colonizes it. IdentityRecord has the structural advantage: the Identity Record already holds verified business identity. Adding transactional readiness is a natural extension.

02

What It Checks

The module validates six dimensions of transactional readiness:

Booking Capability

Does the business have a machine-callable booking endpoint? Calendly, Acuity, Square Appointments, Mindbody, or custom systems.

Quote / Estimate Capability

Can a customer or AI agent request a quote programmatically? Structured forms, APIs, or chat intake with booking intent.

Payment Capability

Can the business accept payment through a machine-callable channel? Stripe, Square, PayPal, Shopify POS, or custom checkout.

Schema Compliance

Does the business emit Action schemas (OrderAction, ReserveAction, QuoteAction) in structured data AI agents can parse?

Communication Readiness

Can an AI agent reach the business through a structured channel with measurable response times?

Identity Verification

Is the business owner verified with a complete Identity Record and recent proof of activity? Already solved by existing modules.

03

The Output

The Identity Record gains a new public status:

Agentic Ready

This business can be transacted with by AI agents.

Not Yet Agentic

This business is not ready for AI-initiated transactions.

This is binary. There is no spectrum. The business either qualifies or it does not.

The status is machine-readable via JSON-LD on the Identity Record, consumable by AI agents via MCP, and visible on the public record URL.

04

Implementation Plan

Phase 1: Foundation

2 weeks

  • Database schema (agentic_readiness table)
  • Backend readiness assessment engine
  • Frontend module page in workplace with status display
  • Public badge on Identity Record
  • JSON-LD agenticReadiness object in record output

Phase 2: Automated Detection

2 weeks

  • Crawl business website for booking/payment/quote endpoints
  • Detect common platforms (Calendly, Square, Stripe, Mindbody)
  • Auto-populate readiness dimensions from detected endpoints
  • Surface gaps with specific remediation guidance

Phase 3: Protocol Integration

2 weeks

  • Emit agentic readiness signals via MCP to Claude
  • Emit via IdentityRecord Protocol Specification to other AI engines
  • Add Action schemas to JSON-LD output
  • Enable AI agents to discover and call verified endpoints

Phase 4: Agency Reporting

1 week

  • Agentic readiness column in agency dashboard
  • Portfolio-level readiness percentage
  • Monthly readiness change tracking
  • Export for client reporting

Total estimated build: 7 weeks. Phase 1 can ship independently.

05

Competitive Position

What no one else has: No incumbent (Yext, Birdeye, SOCi, BrightLocal) validates transactional readiness. No GEO startup has connected identity verification to transaction capability. The agentic commerce protocols are live but the trust layer does not exist.

What IdentityRecord has: The Identity Record already holds verified business identity. The six existing modules already prove the business is real and operating. Adding transactional validation is a natural extension. First-mover on "Agentic Ready" owns the vocabulary.

The category claim: IdentityRecord moves from "Business Identity Management" to "The eligibility layer for AI-era commerce." Agentic Readiness is what makes this claim real.

06

Risks and Mitigants

RISKMITIGANT
AI agents may not transact at scale for 12-18 monthsThe status itself is valuable now as a trust signal, even before agents transact at volume
Businesses may not have booking or payment endpointsThe module surfaces the gap and guides remediation. The 'Not Yet Agentic' status creates urgency
Schema standards for agentic commerce are evolvingBuild on existing schema.org Action types. Update as standards mature
Detection of endpoints may be impreciseStart with manual declaration. Add automated detection in Phase 2. Verify over time
07

Success Metrics (90 days post-launch)

Records with Agentic Readiness assessed500+
Records achieving Agentic Ready status100+
Agency clients tracked for readiness50+
First confirmed AI agent transaction1
08

Decision Required

Justin, review this brief and confirm:

  1. Scope: Are the six dimensions correct, or should any be added or removed?
  2. Naming: "Agentic Ready" as the public status, or a different term?
  3. Phasing: Start with Phase 1 (2 weeks) and ship, or build all four phases before launch?
  4. Score integration: Add to the existing 100-point Trust Score, or keep as a separate binary status?
  5. Timeline: Proceed immediately, or sequence after another priority?

IdentityRecord | Agentic Readiness Module Brief

April 2026 | Confidential