Data strategy · capacity intelligence · June 2026

The data moat: capacity intelligence, not catalog listings

Static catalogs tell you what a supplier once sold. Real time capacity × schedule tells you what you can actually buy now, and that dataset only exists where trust rails make it safe to post. That is the structural moat: not scraped listings, but live, escrow backed, verified capacity intelligence.

13
live verticals
212
spec fields
377
canonical parts
∞
scrape proof
The data stack · from raw signal to sellable intelligence
RAW SIGNALS capacity · schedule · specs certs · machine lists · reviews private · perishable · high value TRUST RAILS KYB · escrow · proof · audit reputation · dispute resolution makes a soft schedule hard STRUCTURED SPEC one spec language across 13 verticals required axes · validators · signatures wrong part prevention by design CAPACITY ORDER BOOK supplier capacity × schedule × trust score unscrapable · tradable · the market INTELLIGENCE PRODUCTS · reference prices · lead time indices · scarcity alerts · demand forecasts buyer demand

Read it: the order book is not a database you can buy or scrape. It is the live output of suppliers posting real capacity inside a trust system. Every completed deal adds reputation, proof, and reference price, which makes the next match faster and the data itself more valuable.

Why this data is unscrapable

Supplier posted, not web crawled
Capacity and schedule come from the supplier’s own system or MPBx onboarding. No public page contains it; no crawler can reconstruct it.
Escrow makes it credible
A posted slot is only tradable once it is backed by escrow terms, milestone releases, and a verified KYB identity. That is infrastructure, not HTML.
Spec validated by default
Every RFQ runs through vertical specific validators (212 fields across 13 pillars). A mismatch is caught before it becomes a wrong part order.
Permissioned and perishable
Capacity changes daily. Historical snapshots are worthless; only live feeds inside the exchange matter, and access is gated by deal stage.

Data products the market will pay for

Revenue lines beyond the take rate
ProductWhat it isWho buys itWhy it scales
Capacity data subscriptionLive order book feeds per vertical: available slots, lead times, price bands.OEMs, traders, procurement platformsThe more suppliers post, the more complete the feed. Buyers pay for visibility their competitors lack.
Reference price indicesTransaction derived benchmarks for common specs (e.g. 2L FR 4, 4680 NCM, R 454B chiller).Finance, commodity desks, buyersEscrow backed prices are harder to game than self reported quotes.
Scarcity / surplus alertsReal time signals of filling slots or idle capacity in a narrow spec corridor.Agents, planners, tradersPerishable supply creates urgency; early signal is arbitrage.
Lead time forecastsVerified production + logistics timelines per supplier and vertical.Supply chain teamsBeats guessing from RFQ replies because it is rooted in actual bookings.
Supplier risk scoresComposite of trust score, on time history, dispute record, cert status.Quality, compliance, financeReputation compounds with every closed deal; new entrants cannot fake it.
The compounding loop · data begets liquidity begets data
1 · More suppliers post capacity 2 · Richer order book better match probability 3 · More closed deals reputation + reference data 4 · Buyers see proof, suppliers see yield 5 · Higher trust, lower friction faster commoditization of slots 6 · Liquidity manufactures itself DATA MOAT

Capital can copy features; it cannot copy accumulated trust + a filled order book overnight. The data moat is structural because the data only exists inside the loop, and the loop only works when trust rails keep it honest.

Internal data strategy narrative · 13 verticals, 212 spec fields, 377 canonical parts as of June 2026 · pairs with the capacity exchange strategy and positioning briefs.