Cowrie Research

atlas-protocol

4 min read

ATLAS Protocol

  • Name: ATLAS Protocol
  • URL: https://github.com/lemonadesocial/atlas-protocol
  • Category: event-discovery and ticketing protocol / agentic commerce infrastructure / vertical marketplace control plane
  • Summary: ATLAS is a vertical event-commerce control plane, not a general machine-payments standard. The useful part is the stack it bundles for one market: organizer-authorized supply ingestion, federated event discovery, schema.org-compatible listings, 402 purchase flows, USDC settlement, cryptographic receipts, and ad-mediated discovery rents.
  • What it does:
    • Defines an event-specific protocol stack for discovery, listing, purchase, settlement, and receipt issuance so software agents can find and buy tickets without bespoke per-platform integrations
    • Uses /.well-known/atlas.json manifests plus a federated registry to expose ATLAS-capable event feeds and capabilities
    • Extends schema.org/Event with ATLAS-specific availability, ticket-type, purchase, and settlement fields so existing structured-data consumers and ATLAS-aware agents can read the same listing surface
    • Uses an HTTP 402 Payment Required purchase flow with hold IDs and expiration windows so agents can reserve inventory, pay, and receive cryptographic purchase receipts
    • Frames settlement as chain-agnostic USDC routing across supported EVM chains, with event metadata pinned to IPFS and later-stage smart contracts for fee routing, tickets, rewards, registry pointers, and promotion settlement
    • Adds organizer-side infrastructure beyond ticket sales, including OAuth-based imports from incumbent platforms, XMTP-based organizer/guest CRM, and a pay-per-sale ad-network that routes promotion revenue to agents and registry nodes
  • Key claims:
    • The whitepaper frames ATLAS as an open protocol for making every event on the internet discoverable, bookable, and settleable by software agents rather than a single marketplace or ticketing frontend.
    • The strongest reusable mechanism is the layered split between discovery (/.well-known/atlas.json + registry), listing (Schema.org JSON-LD extensions), purchase (HTTP 402 + holds), settlement (USDC on supported EVM chains), and receipts (signed proof of purchase pinned to IPFS).
    • The organizer-intake model matters analytically: ATLAS says it does not need platforms to integrate first because organizers can connect incumbent event accounts via OAuth, which makes it a Plaid-style bottom-up aggregation strategy rather than a pure standards-body play.
    • The protocol-native ad-network is a distinct control surface, not just a growth feature. The fee spec separates ordinary ticket-fee routing from promotion-bid routing and explicitly pays discovery agents and registry nodes when promoted inventory converts.
    • Progressive decentralization is explicit but incomplete. The trust-critical components ATLAS wants to move onchain are fee splits, ticket validity, reward payout integrity, and registry pointers; ranking, connector sync, frontend UX, and inference are explicitly kept centralized.
    • Governance remains Lemonade-led for early phases, then moves through advisory-board and steering-committee stages toward a foundation and token-holder governance, so the protocol should still be analyzed as an early operator-shaped system rather than a credibly neutral network.
    • The payment layer is directionally clear but slightly unsettled in the current docs set: the whitepaper and settlement spec center Machine Payments Protocol (MPP) plus Shared Payment Tokens for fiat, while the repo README also markets direct onchain payment via x402-compatible flows. That inconsistency is itself a useful signal that ATLAS may ultimately sit above, or flex across, more than one machine-payment transport.
    • ATLAS cleared the bar for the active corpus because it makes a vertical commerce market legible as its own reusable control plane: supply ingestion, event normalization, search/index policy, hold-and-payment flow, chain-selection logic, receipt issuance, organizer reward routing, and ad-mediated discovery rents.
  • Whitepaper: Yes. The project publishes a first-party whitepaper in markdown in the public repository (whitepaper/WHITEPAPER.md); this pass also reviewed the official settlement, fee-economics, decentralization, governance, and README materials. See ../whitepapers/atlas-protocol-primary-sources-2026-05-12.md.
  • Sources:

Internal linkages

Graph View