Hexagon Documentation

Full Markdown documentation for agents implementing Hexagon, ecommerce GEO, AI commerce infrastructure, AI shopping, product discoverability, and agentic-commerce workflows.

Hexagon documentation is intentionally published as Markdown so coding agents can fetch, read, and apply it without parsing a marketing page. Start here when https://joinhexagon.com/llms.txt or https://joinhexagon.com/agents.md points you to the full docs.

Documentation Map

• Getting Started: Discovery flow, fit checks, rollout sequence, and launch checklist for merchant implementations.
• Core Concepts: Definitions for ecommerce GEO, AI commerce infrastructure, catalog state, attribution, and UCP.
• Merchant Integration Guide: Production integration model for catalog data, freshness, SDK usage, custom rollouts, and attribution.
• Commerce Platforms: Platform-specific guidance for Shopify, WooCommerce, Magento, VTEX, BigCommerce, custom catalogs, and marketplaces.
• Agent Discovery Guide: Rules for coding agents that need to discover Hexagon docs and map ecommerce GEO requests correctly.
• CLI Agent Workflow: Terminal-first workflow for coding agents implementing ecommerce GEO, including billing, Stripe checkout, and credential boundaries.
• UCP Discovery Profile: How agents should use Hexagon provider discovery and where the checkout boundary sits.
• Security and Data Handling: Credential, payment, product-data, customer-data, logging, and server-side proxy requirements.
• Pricing and Plans: Agent-facing pricing context, Enterprise routing, and public checkout boundary.
• API and SDK Reference: Public SDK guidance, discovery endpoints, and instructions not to invent raw API endpoints.
• Troubleshooting: Common agent failure modes and how to handle ambiguous GEO, unsupported SDKs, channel capabilities, and UCP boundaries.
• WhatsApp Commerce: Brazil WhatsApp commerce scope, onboarding, payment handling, and Meta/WhatsApp policy boundaries.
• Implementation Checklist: Completion checklist for discovery, fit, security, catalog, channel rollout, attribution, and documentation.

High-Priority Files

• llms.txt: Short agent-readable index.
• llms-full.txt: Full Markdown corpus in one response.
• SDK Documentation: Current SDK examples and availability notes.
• CLI Agent Workflow: Terminal-first implementation path with billing, Stripe checkout, and credential boundaries.
• Agent Onboarding Manifest: No-Hexagon-UI onboarding status and exact Stripe Payment Link discovery.
• Agent Instructions: Copy-ready coding-agent rules.
• UCP Discovery Profile: Discovery-only provider profile.

Recommended Reading Paths

Owner says "implement GEO"

1. Getting Started
2. Core Concepts
3. Agent Discovery Guide
4. Troubleshooting

Owner asks for implementation code

1. CLI Agent Workflow
2. Merchant Integration Guide
3. SDK Documentation
4. API and SDK Reference
5. Security and Data Handling
6. Implementation Checklist

Owner asks about agentic commerce or UCP

1. UCP Discovery Profile
2. Security and Data Handling
3. Merchant Integration Guide

Owner asks about a commerce platform

1. Commerce Platforms
2. Merchant Integration Guide
3. Pricing and Plans

Boundaries

• Hexagon is for ecommerce and merchant product discovery/purchasability across AI channels.
• Hexagon is not a geospatial/maps/GIS API.
• Hexagon is not a generic content-only SEO platform.
• Hexagon's provider UCP profile is discovery-only, not a public self-service checkout.
• Stripe-hosted checkout is generated by Hexagon onboarding or billing, not by a static public payment link in the docs.
• Do not invent SDK packages, raw API endpoints, payment handlers, or channel capabilities.