wagecore
← Wagecore

AI labor economics · tracker

Capability is here. Viability is the question.

The industry has spent hundreds of billions proving AI can do the work. Whether it pays — to actually run, role by role — is a different number. This page is that number on open methodology: the macro proof first, then every role costed.

Role numbers are the matrix-derived read at a representative cell (Tier 2 US city × mid experience). Your mix will differ — compute your own Wagecard for the precise read.

The industry proof

Hundreds of billions bought the capability. The payback isn't showing up.

The capital pouring into AI infrastructure is on the record. What AI earns back mostly isn't. Same pattern as every role below — capability is the easy part; viability is the question.

The industry proof

The capability is bought. What it earns back, the market mostly can't see yet.

$372B
Hyperscaler capex, 2025

Amazon, Alphabet, Microsoft, Meta — filed FY2025

$52B
AI revenue they disclose

Two of the four disclose none at all

$194B
Nvidia data-center revenue

On $6B of its own capex — the supplier wins

Public hyperscalers — capex vs disclosed AI revenue

Amazon

Capex (invested)$128B

FY2025 capex (company-wide)

AI revenue (earned)$15B

AWS AI revenue run-rate, Q1 2026

Amazon FY2025 capex & AWS AI run-rate (Yahoo Finance) (2026-04-09)

Alphabet (Google)

Capex (invested)$91.4B

FY2025 capex

AI revenue (earned)Not disclosed

No AI-specific revenue line

Alphabet Q4 & FY2025 earnings release (2026-02-04)

Microsoft

Only one to disclose AI revenue and AI capex
Capex (invested)~$80B

FY2025 AI data-center capex

AI revenue (earned)$37B

AI business run-rate, Q3 FY2026

Microsoft FY2025 AI data-center capex (CNBC) (2025-01-03) · Microsoft Q3 FY2026 newsroom (AI run-rate $37B) (2026-04-29)

Meta

Capex (invested)$72.2B

FY2025 capex

AI revenue (earned)Not disclosed

No AI-specific revenue line

Meta Q4 2025 results (8-K, exhibit 99.1) (2026-01-28)

Nvidia

Sells the shovels
Capex (invested)$6.0B

FY2026 capex (own property & equipment)

AI revenue (earned)$193.7B

FY2026 data-center revenue

Nvidia Q4 & FY2026 earnings release (SEC) (2026-02-25)

Private frontier labs — capital raised vs revenue run-rate

OpenAI

Capital raised$122B

Capital raised, Mar 2026 round

Revenue run-rateest.~$25B

Revenue run-rate, Feb 2026

OpenAI $122B round (Bloomberg via Yahoo Finance) (2026-04-02) · OpenAI ~$25B run-rate (The Information via Yahoo Finance) (2026-02-15)

Anthropic

Capital raised$65B

Series H, May 2026

Revenue run-rateest.~$47B

Revenue run-rate, May 2026 (self-reported)

Anthropic Series H announcement ($47B run-rate) (2026-05-28)

xAI

Capital raised$20B

Series E, Jan 2026

Revenue run-rate$3.2B

FY2025 revenue (consolidated, filed)

xAI Series E announcement (2026-01-06) · xAI FY2025 revenue, SpaceX S-1 (via Yahoo Finance) (2026-05-21)

How these numbers work

Figures are compiled from company SEC filings, official earnings releases, and named financial reporting as of June 2026 — each cited in the row above. They are not like-for-like: capex is cash committed in a fiscal year; an AI-revenue figure is an annualized run-rate a company chose to disclose, not booked annual revenue; capital raised is balance-sheet, not spend. We do not net them — one “profit” number across these bases would be wrong. Where a company discloses no AI-specific revenue, we show “Not disclosed” rather than estimate it. Two reasons the company-level picture stays murky: most AI revenue isn't broken out, and the AI economy is circular — the same dollars cycle between cloud providers, chipmakers, and labs. Figures tagged est. rest on press or self-reported estimates, not a filing. Macro framing inspired by isaiprofitable.com; figures and sources are our own.

At the company level the payback is mostly undisclosed — and where it shows, the spend dwarfs it. At the role level it's calculable. That's the rest of this page.

Why it resolves at the role level

Capability is cheap. Viability is the question.

They say

AI runs a knowledge-work role for the price of a few API calls — the token bill is rounding error against a salary.

The math says

Across these 15 roles, raw token spend is about 45% of what the AI substitute actually costs to operate — oversight, retries, orchestration, and integration carry the rest. Mean substitution exposure is 41/100, and 57% of the hours stay human-led or human-critical.

What the math says, in aggregate

Most knowledge work is augmentation territory, not replacement

Across 15 roles, the average economic substitution exposure is 41 / 100. By hours, 6% of the typical week lands in fully-replaceable territory — the rest stays human-led, human-critical, or AI-augmented.

Roles costed

15

Each at a representative Tier 2 / mid cell.

Average exposure

41 / 100

Lower = more human-leveraged. 57% of hours stay human-led or human-critical.

Fully-replaceable share

6%

Of the average week, by hours, across all roles.

Where the hours sit, on average

Replaceable6%
AI-augmented38%
Human-led + AI-assisted24%
Human-critical33%

Role by role

What AI actually costs to run, per role

Sort by exposure, by what the market pays, or by the gap between pay and AI run-cost. Every row opens the full methodology read.

Sort by

Exposure runs 0–100; lower means more of the role's hours stay human-leveraged. AI run-cost is what it costs to run AI across the same task-week — tokens, oversight, retries, integration — and excludes human-critical hours the model doesn't hand to AI. It is a run-cost, not a savings figure.

Computed against capability matrix v1 · model v1-mvp · representative cell (Tier 2 / mid). Median pay from BLS OEWS blended with market compensation data. Numbers refresh when the matrix refreshes. Open methodology at /methodology.

FAQ

Questions the number raises

Is this an AI-risk score?
No. The headline number is Economic Substitution Exposure (ESE), 0–100 — an hours-weighted estimate of how economically substitutable a role's work is at today's capability and cost. It is not a replacement probability and not a risk score. Lower means more human-leveraged, not 'safer'.
Where do the numbers come from?
Median pay is BLS Occupational Employment and Wage Statistics blended with market compensation data, at a Tier-2 US city × mid-experience cell. Capability, reliability, oversight time, error cost, and integration overhead come from the open capability matrix. The engine math — substitution mapping, operational cost, salary benchmark — is published on the methodology page.
Why is the AI run-cost so much lower than the pay?
Because it only covers the hours AI actually runs. Tasks classed human-critical carry zero AI cost — the model doesn't do them. And inside the hours AI does run, oversight and retries usually cost more than the tokens. Cheaper per substitutable hour is not the same as viable for the role: that is exactly what the exposure score and the four-class distribution are there to show. AI run-cost is a run-cost, not a savings figure.
Why these roles, and why one representative cell?
These are the US knowledge-work roles modeled in the current capability matrix. Each row is computed at one representative cell (Tier-2 × mid, 6 hours/week per task) so roles are comparable — the same cell each role's detail page renders. Your real geo, experience, salary, and task mix will differ; compute your own Wagecard for the precise read.

Your week isn't the representative cell. Get the precise read.

Pick your geo, experience, salary, and the task mix that fits your actual role. Anonymous preview before sign-in; full Wagecard with a free account.