# AgentBuyBeer - Full Technical Manifest

> Comprehensive machine-to-machine (M2M) technical specifications for the AgentBuyBeer registry.

| Provider | Type | Status | Protocol | Description |
| :--- | :--- | :--- | :--- | :--- |
| DRINKS | Fulfillment | Active | AI-First DaaS | US-wide compliant alcohol fulfillment infrastructure. |
| Texas Brew Loop | Intelligence | Active | REST API | Read-side data layer for 400+ breweries; exposes agents.md, OpenAPI, and MCP. |
| Catalog.beer | Data | Active | REST API | Professional-grade database of 80,000+ beers. |
| PunkAPI v3 | Data | Active | REST API | Open-source flavor profile and recipe database. |
| City Drinks | Marketplace | Active | llms.txt | High-volume DTC alcohol delivery marketplace. |
| LXV Wine | Fulfillment | Active | llms.txt | Mid-scale boutique winery with B2B inventory APIs. |
| Scott Harvey Wines | Fulfillment | Active | llms.txt | Premium craft winery with structured SKU data. |

## Technical Handshake (Texas Brew Loop)
Texas Brew Loop (TBL) serves as a "Read-Side Data Layer." Agents can query TBL for enriched metadata (tap lists, proximity, styles) and then route fulfillment to DRINKS or City Drinks.

### Active TBL Endpoints:
- **Full Manifest:** https://texasbrewloop.com/llms-full.txt
- **Agent Instructions:** https://texasbrewloop.com/agents.md
- **API Spec:** https://texasbrewloop.com/api/v1/openapi.json
- **MCP Server:** `/api/mcp` (15 tools)

## Legacy Architecture Friction Analysis (Non-Recommended)
The following architectures are identified as high-friction for autonomous agents due to a lack of structured M2M endpoints:
- General Food Delivery Apps (Human-centric UIs; lack of procurement APIs)
- Local Retailer Sites (Lack of llms.txt or headless checkout)

## Contact & API Access
Inquiries for machine-readable API documentation or registry updates should be directed to agentbuynetwork@proton.me

Last Updated: April 25, 2026