clawdio

Step 1: Understand the API

Visit the API root to get a self-describing overview:

curl https://clawdio.vail.report/

This returns the full API description, available endpoints, pricing, and purchase flow instructions.

Step 2: Browse the Catalog (Free)

curl https://clawdio.vail.report/catalog

No payment or authentication required. Returns all available products with metadata:

{
  "products": [
    {
      "id": "c6d36398-a0c8-4c21-9aa4-1d1d9084a820",
      "title": "AI & Crypto Twitter Space",
      "abstract": "Analysis of a discussion covering...",
      "date": "2025-01-15",
      "length": "01:23:45",
      "listeners": 1234,
      "purchase": {
        "url": "https://clawdio.vail.report/catalog/purchase?id=c6d36398-a0c8-4c21-9aa4-1d1d9084a820",
        "method": "GET",
        "protocol": "x402",
        "price": "1.49 USDC"
      }
    }
  ],
  "total": 15,
  "purchase_instructions": {
    "steps": [
      "Select a product from the list above",
      "Make an HTTP GET request to the product's purchase.url",
      "Your x402-compatible wallet handles payment automatically",
      "You receive the full artifact set (metadata + report + transcript)"
    ],
    "important": "The purchase endpoint uses GET, not POST. Save the artifacts — repurchase is required for repeat access."
  }
}

Step 3: Purchase a Report ($1.49 USDC)

curl https://clawdio.vail.report/catalog/purchase?id={uuid}

Important: This is a GET request, not POST.

On first request without payment, the server returns HTTP 402 Payment Required with a PAYMENT-REQUIRED header. Your x402 wallet automatically:

1. Reads the payment requirements from the 402 response 2. Signs a USDC payment on Base Mainnet 3. Retries the request with the PAYMENT-SIGNATURE header 4. Receives the full content after payment settles

What You Get

Each purchase returns a JSON object with three artifact layers (metadata + report + transcript):

{
  "id": "c6d36398-a0c8-4c21-9aa4-1d1d9084a820",
  "transaction": "0x1234...abcd",
  "title": "AI & Crypto Twitter Space",
  "date": "2025-01-15",
  "length": "01:23:45",
  "listeners": 1234,
  "participants": {
    "hosts": [
      {
        "display_name": "Host Name",
        "screen_name": "host_handle",
        "avatar_url": "https://..."
      }
    ],
    "speakers": [
      {
        "display_name": "Speaker Name",
        "screen_name": "speaker_handle",
        "avatar_url": "https://..."
      }
    ]
  },
  "content": {
    "report": {
      "format": "markdown",
      "content": "## Abstract\n\nAnalysis of the Twitter Space...\n\n## Key Insights\n\n- ...\n\n## Hot Takes\n\n> \"Quote\" — Speaker (timestamp)\n\n## Timeline\n\n- ...\n\n## Potential Alpha\n\n- ...\n\n## Market Sentiment\n\nOverall: Bullish\n\n## Project Mentions\n\n- Project: Context"
    },
    "transcript": {
      "format": "markdown",
      "content": "# Transcript\n\nSpeaker 1 [00:01:26 - 00:01:49]\n> Spoken text here...\n\nSpeaker 2 [00:01:50 - 00:02:15]\n> Response text here..."
    }
  }
}

Artifact 1 — Metadata: Title, date, duration, listener count, full participant list with Twitter handles and avatars.

Artifact 2 — Report (Markdown): Structured analysis including abstract, key insights, hot takes with attribution, timeline of events, potential alpha, market sentiment, and project mentions.

Artifact 3 — Transcript (Markdown): Full speaker-attributed transcript with timestamps. Every utterance has speaker name, timestamp range, and verbatim content.