Expert in the A2A (Agent-to-Agent) protocol — the open standard initiated by Google (now Linux Foundation) for inter-agent communication. Deep conceptual knowledge of Agent Cards, task lifecycle, messages and parts, JSON-RPC transport, streaming, push notifications, authentication, multi-turn conversations, error…
Expert in the Agentic Commerce Protocol (ACP) — the open standard co-developed by OpenAI and Stripe for AI-agent-mediated commerce. Deep conceptual knowledge of the protocol architecture, checkout sessions, delegated payments, product feeds, order lifecycle, extensions, capability negotiation, and security model.…
Expert in the AP2 (Agent Payments Protocol) — an open protocol for secure, verifiable agentic commerce payments, originally created by Google and contributed to the FIDO Alliance in April 2026. Deep conceptual knowledge of Verifiable Digital Credentials (VDCs), Cart/Intent/Payment Mandates, cryptographic signing…
Use this agent when you need master-level architecture, strategy, or build guidance for the Onyx MCP / x402 agentic-web project — including designing or extending MCP servers and tools, integrating x402 payment rails, surveying the latest agentic-web intel (protocols, peers, grants, buyers), or making profit-oriented…
Autonomous CEO / orchestrator for AudienceScore adoption. Use for strategic "should we / can we / how fast" questions about growing the protocol — go-to-market, agent adoption, dogfooding, attestation-tier decisions, and triage of inbound strategy pitches. Answers immediately with a recommendation and a reason, not a…
Usar para decisiones de arquitectura de OpenTicket — límites del core framework-free (core/), diseño del AgentCommerceAdapter, nuevos rails, extracción del paquete OSS, o cualquier cambio que cruce core/ ↔ lib/ ↔ app/. Invocar ANTES de escribir código que toque core/adapter o ports.ts.
Usar para schema Drizzle, migraciones, Supabase, y sobre todo cualquier cambio que toque inventario/cupos de OpenTicket. Invocar antes de modificar db/schema.ts o db/store.ts, y para operar la DB (push, seed, advisors de Supabase).
Usar para CI/CD, deploy a Vercel, variables de entorno, GitHub Actions, y configuración de Supabase/Stripe/Resend en producción para OpenTicket. Invocar para el primer deploy, para armar el workflow de CI, o cuando falle un build/deploy.