Agentic Holding Studio
Agentic Holding Studio runs three autonomous, text-first micro-businesses alongside Protocol Dispatch under one CEO governance contract: AgentReadiness (/readiness), AgentStack Radar (/radar), and QuotePacket (/quotes). Every page is semantic HTML with JSON-LD, feeds, and dual human/agent subscriptions.
- One CEO governance loop runs all properties in deterministic Cloudflare Worker code so customer tools never stall on LLM token limits.
- Outbound emails, sponsorship outreach, and live deployments stay behind an explicit human approval gate.
| Business | Primary Job | Human Entry | Agent / API Entry | Support |
|---|---|---|---|---|
| AgentReadiness | 100-point SEO / GEO / AEO HTML scanner and llms.txt + JSON-LD generator | /readiness | POST /api/readiness/audit | /readiness/support |
| AgentStack Radar | Curated MCP server & deterministic workflow directory + release feeds | /radar | GET /api/radar/entries | /radar/support |
| QuotePacket | Multi-vendor RFQ & contractor quote normalization matrix | /quotes | POST /api/quotes/compare | /quotes/support |
| Protocol Dispatch | Public field guide and update wire for Shadow Protocol 64 (https://shadow-protocol-64.baileyj79.workers.dev) | /dispatch | GET /llms.txt | /dispatch/support |
How are the three micro-businesses governed?
Agentic Holding Studio runs three autonomous, text-first micro-businesses alongside Protocol Dispatch under one CEO governance contract: AgentReadiness (/readiness), AgentStack Radar (/radar), and QuotePacket (/quotes). Every page is semantic HTML with JSON-LD, feeds, and dual human/agent subscriptions.
How do humans and AI agents subscribe across the studio?
Humans submit the consent form on any business page. Agents POST JSON to /api/subscribe with channel set to agent, an email or https URL, and an optional topic filter.
Subscribe (Human or AI Agent)
Agents subscribe by posting JSON to /api/subscribe with {"channel":"agent","address":"https://...","topic":"all","consent":true} and polling /llms.txt and /feed.json.