One API.

Orbyt Intelligence. AI compensation, decoded. It ships as six engines for the AI labor market: AI Role Taxonomy (598 roles, BLS SOC mapped), AI Skill Premiums (dollar premium per skill), AI Skill Half-Life (decay curves on each premium), AI Comp by Funding Stage (seed through public), AI Company Signals (hiring intent + comp pressure + attrition), and AI Hiring Velocity (posting volume + time-to-fill + salary drift). All six surface through 20 REST endpoints and one MCP server with six locked tools. Lineage on every response. Built for AI research teams, HR tech platforms, and newsrooms.

Orbyt Intelligence is the only compensation platform built for AI roles first, and the only one with six purpose-built engines instead of a single salary lookup. 598 specialized job titles (Levels.fyi tracks roughly 100). Quantified skill premiums with confidence intervals and decay curves (no one else publishes these). Funding-stage compensation bands from seed to public per role. field-level provenance via /lineage on every data point. MCP server returning Decision-Ready Responses with citation.request_id traceability: drop into Claude Code, ChatGPT, or any MCP client.

AI Role Taxonomy resolves role identities (598 roles, eight families, eight seniority bands, BLS SOC codes, related-role graph). AI Skill Premiums quantifies the dollar premium each skill commands by role and city, with 95% CIs. AI Skill Half-Life models how fast each premium is decaying using exponential, logistic, or plateau curves. AI Comp by Funding Stage breaks comp down across seven stages from seed to public, with explicit equity-vs-cash math. AI Company Signals tracks per-company hiring intent, comp pressure, attrition risk, AI maturity, and pay transparency posture. AI Hiring Velocity measures posting volume, time-to-fill, salary drift, and competitive intensity per role × city.

The MCP server at /api/v1/intelligence/mcp is a JSON-RPC 2.0 endpoint exposing six locked tools: list_capabilities, analyze_compensation, analyze_skills, analyze_market, discover_roles_and_cities, find_adjacent_opportunities. Every tool returns a Decision-Ready Response with a quotable answer sentence, primary + supporting data, methodology citation, follow-up suggestions, and honest limitations. Stdio transport for Claude Code, HTTP transport for any agent. Same API key. Pro plan and above. See /orbyt-intelligence/mcp for the full integration guide.

Free is 1,000 requests a month at 60 requests per minute, with no card. AI Role Taxonomy engine (598 roles, 81 cities, BLS SOC mapping). The calculate and search endpoints. The published BLS wage benchmark that travels beside every estimate. CORS enabled. An API key IS required, because the monthly limit is counted per user and an anonymous request cannot be. Upgrade to Pro for the MCP server and the /lineage provenance endpoint.

Pro at $99/month adds 300 requests per minute, 250,000 requests a month, the MCP server, the /lineage provenance endpoint, restricted API keys with per-engine scopes, and priority support. 5 seats included. Most teams upgrade when they want to wire Orbyt into Claude Code via MCP, or when they need provenance on every figure they cite.

Ultra at $199/month includes 1,500 requests per minute, 500,000 requests a month, the company leveling catalog, the annual compensation reports, dedicated support, and custom data requests. 15 seats included.

Yes. Every response includes a citation field ready to quote verbatim, plus an assumptions array explaining methodology. The Dataset schema markup is verified and indexed by Google Dataset Search and Perplexity's answer engine. Suggested citation: "Orbyt Intelligence, May 2024. https://www.orbytlabs.ai/intelligence"

The salary figures are computed estimates, not observed wages: a national role baseline scaled by BEA Regional Price Parities. The published wage data Orbyt holds is BLS Occupational Employment and Wage Statistics, and Department of Labor H-1B Labor Condition Application filings (a filed minimum visa base wage, not market pay). Where BLS publishes a wage for the occupation a role maps to, it is shown alongside the estimate as a separate benchmark, labelled with its occupation code, metro area and worker count. Full methodology is published at /orbyt-intelligence/methodology.