AudioAlpha

API & MCP Documentation

Access AudioAlpha data programmatically via our REST API or connect directly to Claude or Grok using MCP (Model Context Protocol).

Generate Your API Key

API keys provide access to both the REST API and MCP integration. Each subscription tier includes different rate limits and endpoint access.

1. 1
2. 2 Find API Access Section Scroll down to the "API Access" card
3. 3 Generate Key Click "Generate API Key" to create a new key
4. 4 Store Securely Copy and store your key securely - it will only be shown once

Keep your API key secret. Never expose it in client-side code or public repositories.

Connect MCP to Claude Desktop

MCP (Model Context Protocol) allows Claude to directly access AudioAlpha data during conversations. Ask Claude about market sentiment, trends, and asset data - it will automatically fetch from AudioAlpha.

Setup Instructions

1. 1 Open Claude Desktop Settings Go to Settings → Developer → Edit Config
2. Add AudioAlpha MCP Server Add the following to your claude_desktop_config.json:

   "mcpServers": {
     "audioalpha": {
       "command": "npx",
       "args": [
         "mcp-remote",
         "https://www.audioalpha.io/api/mcp?apiKey=sk_live_your_key"
       ]
     }
   }
   

3. 3 Replace API Key Replace sk_live_your_key with your actual API key from /account
4. 4 Restart Claude Desktop Save the config file and restart Claude Desktop to apply changes

Example Prompts

"What's the current sentiment for Bitcoin?"

"Show me the top rising assets from yesterday's podcasts"

"What are the main themes being discussed in market podcasts this week?"

Tip: You can also simply ask Claude to connect and provide your API key - it will guide you through the latest setup instructions.

Connect MCP to Grok

MCP (Model Context Protocol) allows Grok to directly access AudioAlpha data during conversations. Ask Grok about market sentiment, trends, and asset data — it will automatically fetch from AudioAlpha.

Custom connectors on grok.com may require Grok Premium.

Setup Instructions

1. 1 Open Grok Connectors Go to grok.com/connectors and click New connector → Custom
2. 2 Name the Connector Use any name you like — for example AudioAlpha
3. Set the Server URL Paste this into the Server URL field, replacing the placeholder with your API key from /account:

   https://www.audioalpha.io/api/mcp?apiKey=sk_live_your_key
   

4. 4 Add Connector Click Add Connector. AudioAlpha will now be available in your Grok conversations.

Example Prompts

"What's the current sentiment for Bitcoin?"

"Show me the top rising assets from yesterday's podcasts"

"What are the main themes being discussed in market podcasts this week?"

Tip: You can also simply ask Grok to use the AudioAlpha connector — it will pull live podcast intelligence on demand.

REST API

Access AudioAlpha data directly via our REST API. All endpoints require authentication via Bearer token.

Authentication

curl -X GET "https://www.audioalpha.io/api/audioalpha-api/market/snapshot" \
  -H "Authorization: Bearer YOUR_API_KEY"

Ticker format: all crypto tickers MUST be suffixed with -USD — e.g. BTC-USD, ETH-USD, SOL-USD. Bare symbols like BTC will not match.

Key Endpoints

/market/snapshot

Daily market-wide sentiment and narrative insights

/ticker/snapshot?ticker=BTC-USD

Asset-specific sentiment and signals (note the -USD suffix)

/market/history?days=30

Market-wide daily snapshot time series (tier-capped: free=7d, alpha=365d, pro=730d, enterprise=1000d)

/ticker/history?ticker=BTC-USD&days=30

Per-asset daily snapshot time series (tier-capped: free=7d, alpha=365d, pro=730d, enterprise=1000d)

/tickers/leaderboard

Top performing assets by various metrics

Historical Data Access

The /ticker/history endpoint returns a time series of daily snapshots. To prevent back-testing on arbitrary historical periods, access is gated by tier:

• Free: up to 7 days, anchored to latest snapshot
• Alpha: up to 365 days, anchored to latest snapshot
• Pro: up to 730 days, anchored to latest snapshot
• Enterprise: up to 1000 days, can pass date to back-date the window

For free / alpha / pro tiers, the date query parameter is silently ignored — the window always ends at the most recent available snapshot. If today has no snapshot yet, the most recent existing snapshot is used as the anchor. Requests exceeding the per-tier days cap are silently capped. The response includes tier_cap, effective_days, start_date, end_date and date_param_honored so clients can see exactly what window was returned.

Snapshot Schedule & Versioning

The daily snapshot is written every day and is typically available by 00:02 UTC at the latest. Because podcasts don't publish on a fixed schedule, a relevant episode is occasionally indexed after a day's snapshot has already been written — when that happens the snapshot is regenerated. The initial end-of-day build carries the label eod_utc; a regeneration increments version_num and changes the label to revised. Both the latest and the original eod_utc version remain available.

Every snapshot-derived response always includes a status field: completed once the snapshot has finished generating (the normal case), or writing while it is being (re)generated — typically during the brief 00:00–00:01 UTC build window. This field is returned regardless of version_info.

Set version_info=true to see exactly which revision you received. The following query parameters control version selection on the snapshot endpoints (/market/* and /ticker/*):

• version_number — which revision to return. Defaults to -1 (the latest authoritative version). Request a specific revision (1, 2, …); if it does not exist for that date, the latest version is returned instead.
• version_info — set to true to include version metadata in the response: both version_num (the revision number) and a human-readable version_label (e.g. eod_utc, backfill, revised). When omitted, neither field is included.
• snapshot_type — asset universe to draw from. Defaults to crypto (tradfi is reserved for a future release).

Range, leaderboard, and personalized feed endpoints (/market/history, /ticker/history, /tickers/leaderboard, /me/feed, /me/favorites/assets) always return the latest authoritative version per date and accept only snapshot_type and version_info.

curl -X GET "https://www.audioalpha.io/api/audioalpha-api/market/snapshot?version_number=-1&version_info=true" \
  -H "Authorization: Bearer YOUR_API_KEY"

Rate Limits

Plan	Per Minute	Per Day	Per Month
Free	5	50	500
Alpha	20	500	4,000
Pro	60	5,000	100,000
Enterprise	300	50,000	Unlimited

See the full comparison of API features by plan on our Pricing page.

Ready to get started?

Generate your API key and start accessing AudioAlpha data programmatically.

Generate API Key