Scrutica
Baidufinancials and operating footprint — geographic revenue split, segment mix, capex / FCF / buyback history, industry placement — sourced from licensed-database extracts and SEC EDGAR, joined to the supply-chain graph through the industry classification.
Where Baidu sits in the compute supply chain: where its revenue comes from, what it spends capital on, and which counterparties move money in and out of the door.
No licensed-database enrichment loaded for this entity — geographic revenue, segments, capital allocation, and industry classification are absent. Coverage rules in the methodology.
Per-chip-class GPU inventory estimates for Baidu, sourced exclusively from peer publications. Per CLAUDE.md DQP §2 every row is is_estimated=true with authority_tier=3 — there is no tier-1 primary source for these numbers.
| Chip class | Deployed (est.) | Stockpiled · frozen | Deployment status | Source |
|---|---|---|---|---|
| Baidu Kunlun P800 | 30.0K | — | Deployed | 2025-04 ↗ |
| NVIDIA H20 | — |
| Unknown |
| no peer estimate |
| Total | 30.0K | 0 | 2025-04 |
Each hop carries its data source, source URL (where one exists), as-of date, and confidence label on the same line as the parent name. When two sources name different parents for the same hop, both sit on the page as alternates — the walker does not pick a winner.
Starting entity — the walker climbs from here, following documented parent / subsidiary edges in the ownership substrate.
Per HKEX / SSE public filing, as-of date not recorded (HIGHtier 1): Handsome Reward Limited is the documented parent.
Per SEC EDGAR, as-of date not recorded (HIGHtier 1): iQIYI, Inc. is the documented parent.
Chain-of-title terminates at Handsome Reward Limited. No further parent is documented — for a public filer that means UBO is the dispersed float; for a state-linked entity it means the chain has reached the sovereign apex.