Sector API

Name: Sector Pulse daily sector rotation record
Creator: Apex Infra LLC
License: https://sector-pulse.app/api-docs

Everything the board knows, programmatic. Live sector ranks, versioned basket rosters, and the full daily rotation history back to July 21, 2026. Built for algos, backtests, and custom dashboards.

Get a key

Every endpoint and every MCP tool needs a key. A call pack is the way in: one call is one credit, credits never expire, and the key arrives by email within a minute of checkout. Packs cover all three endpoints, the rotation record included. The founding tier adds unlimited calls at the rate limit and a Pro membership.

2,000 calls for $10 6,000 calls for $25 Founding tier, $39/mo with Pro

What you can do with it, in plain English

The API is the same data that is behind the board, delivered wherever you want it: the live sector ranks, the names in each basket (versioned, so a list never changes under you), and the day-by-day history of every sector's rank and move. Alerts stay in the Pro app; the API does not push anything. It is for when you want to ask questions of the data yourself.

The easy way in is Claude or ChatGPT: paste one address into the connector settings (see MCP server below) and from then on you type questions. Things members do with it today, no code:

“Which sectors have climbed the most over the last five sessions, and which names drove each one?” A short answer with tickers, not a chart to squint at.
“Give me a two-line morning plan from the 9:45 snapshot: the strongest two sectors, the weakest two, and the names leading each.” The same question every morning, thirty seconds.
“How often did the sector ranked #1 at 9:45 still rank in the top 5 at the close?” An edge question, answered from the history with its sample size.
“Here are the trades I took today. Which were in a top-5 sector at the time and which were not?” A journal that checks your entries against the tape.
“Give me the Semi Architecture basket as a list I can paste into TradingView.” Rosters straight into your own watchlists.

If you trade off the board and the alerts and that is enough, Pro is enough. The API earns its place the day you want the data to answer a question the app does not show, or you want it inside your own tools.

Authentication

Send your key in the x-api-key header on every request. Keys are personal; do not share or embed them client-side. Need a key? The packs are at the top of this page.

curl -H "x-api-key: SPK-YOURKEYHERE" \
  https://sector-pulse.app/api/v1/sectors

Rate limit

10 requests per minute per key. That covers a full three-endpoint scan every 15 seconds of the trading day. Responses beyond the limit return 429; back off and retry. On a call pack, one request is one credit.

GET /api/v1/sectors

The live board. All 30 baskets with session-aware aggregates, three rank bases per sector: rank (session-aware, re-bases at 4pm ET), closeRank (regular-session basis, stable through after-hours), and prevCloseRank (yesterday, for deltas).

GET /api/v1/sectors

{
  "asOf": "2026-08-26T15:40:02.113Z",
  "basis": "live",
  "sectors": [
    {
      "id": "nuclear-uranium",
      "label": "Nuclear & Uranium",
      "pct": 2.96,
      "median": 2.1,
      "breadth": { "up": 7, "down": 1, "total": 8 },
      "rank": 1,
      "closeRank": 1,
      "prevCloseRank": 9,
      "green": true,
      "session": "regular"
    }
  ]
}

GET /api/v1/roster

Versioned basket membership. Rosters are immutable per version: any membership change bumps the version, so point-in-time joins against history stay honest. Includes the share-class alias map (GOOG resolves to GOOGL, and so on).

GET /api/v1/roster            → current roster (version, baskets, aliases)
GET /api/v1/roster?version=2  → that exact historical roster, immutable

GET /api/v1/history

Daily per-sector history back to 2026-07-21 (July 21 through 30 is close-ranks-only; the response marks its basis honestly). Intraday 5-minute rank snapshots from 2026-08-19. Any key: the founding tier or a call pack.

GET /api/v1/history?date=2026-08-21             → that day's sector table
GET /api/v1/history?date=2026-08-21&intraday=1  → plus 5-min intraday rows

MCP server (for Claude, ChatGPT, Cursor, and agents)

The same three endpoints as tools over the Model Context Protocol, Streamable HTTP, at /api/mcp: get_sectors (the live board), get_roster and get_history. All three take your key, sent as the same x-api-key header. Usage and rate limits are shared with the REST endpoints.

{
  "mcpServers": {
    "sector-pulse": {
      "url": "https://sector-pulse.app/api/mcp",
      "headers": { "x-api-key": "SPK-YOURKEYHERE" }
    }
  }
}

ChatGPT and claude.ai: their connector screens take a URL and no header, so put the key in the address instead: https://sector-pulse.app/api/mcp?key=SPK-YOURKEYHERE. In ChatGPT that is Settings, Connectors, Create, with authentication set to none; in claude.ai it is Settings, Connectors, Add custom connector.

Clients that only speak stdio can bridge with npx -y mcp-remote https://sector-pulse.app/api/mcp --header "x-api-key: SPK-YOURKEYHERE". Machine-readable descriptions: openapi.json and llms.txt.

With TradingView in Claude

TradingView has its own MCP server (their Essential plan or above, signed in with your TradingView account). Connect it and Sector Pulse in the same Claude session and one message can read the board here and act in TradingView there. Three prompts to paste as written.

Use Sector Pulse get_sectors for today's top three baskets, then get_roster for each,
and create a TradingView watchlist named "Sector Pulse top 3" with every name in them.

For every name in the Semi Architecture basket (Sector Pulse get_roster), set a
TradingView alert that fires when the price crosses above yesterday's high, mobile push,
auto-deactivate after the first fire.

Pull Sector Pulse get_history for the last ten sessions, pick the basket that climbed
the most, then fetch OHLCV for each of its names from TradingView and tell me which names
led the basket and which lagged it.

The second prompt puts a plain price alert in TradingView. Pro alerts here are the same level with the volume condition, the sector context and the record behind them; the two sit well together. A walkthrough for the whole routine is in the guide How to use sector rotation in Claude with TradingView.

Founding tier

$39/month, Sector Pulse Pro membership included, 10 founding spots, price locked for as long as you stay. Your key arrives by email within a minute of checkout. Current founding Pro members add the API for $27/month on top of their existing plan.

Claim a founding API spot ($39/mo, Pro included)

Add the API to your founding Pro membership ($27/mo), verified against your Pro key.

Every tier side by side on the pricing page.

Pay as you go

Prepaid call packs for developers and agents, API only: $10 for 2,000 calls, $25 for 6,000. One call is one credit on every REST endpoint and MCP tool; credits never expire. You get one email when 10% is left, and calls past zero return 402 with a top-up link until the next pack. Buy a pack on the pricing page (the key arrives by email within a minute) or top up an existing key.

Roadmap

Founding members steer it. First up: multi-day aggregation parameters on the history endpoint. Request anything by replying to any Sector Pulse email or in the founding Discord.

Terms

The API serves Sector Pulse's own derived analytics: basket ranks, aggregates, and rotation history computed by us. It is an educational tool, not financial advice, and nothing served here is a recommendation to buy or sell any security. Data may be delayed or incomplete. Keys are for your own applications; reselling or redistributing the feed itself is not permitted. © 2026 Sector Pulse, a product of Apex Infra LLC.

Anything broken or unclear: support@apexinfrallc.com, answered same day.