AI market share: observed enterprise provider coverage
Compare the share of covered companies naming each AI model provider. Filter the sample, inspect the source evidence, and embed the dated chart.
Reviewed coverage sample · source reviews to (UTC)
Real public-source records, manually reviewed. This is a dated snapshot, not a continuous live feed or a representative market survey.
Share of covered companies
Source reviews 2026-09-10 to 2026-10-15 · 3 distinct companies in the selected model-provider sample.
Each company counts once per provider. Shares can total more than 100% because companies can disclose multiple providers.
Time coverage
Observation period
Covered companies
Comparability
2026-09-10 to 2026-10-15
3
Assembled sample with individual review dates
Earlier months
Unavailable
No comparable company panel
This assembled sample does not establish a monthly trend. Company-size values are not provided by these model-provider disclosures.
Delivery route: not established
The records name providers, but do not establish direct API use versus Azure OpenAI, Bedrock, or Vertex. All 8 records remain unclassified by delivery route; no route split is inferred.
Public-source observations. Observation dates are review dates, not adoption dates.
Company
Vendor / signal
Industry / scope
Observed (UTC)
Evidence
Intercomintercom.com
OpenAIPresence observed
Customer service softwareDefault US-hosted service: AI processing
The numerator is the distinct companies naming a provider. The denominator is the distinct companies naming any included model provider in the selected sample. A company can appear in more than one numerator, so shares may total more than 100%.
OpenAI and Anthropic market share
This is an observed-coverage comparison, not a total-market estimate. The small sample was selected for public evidence and is not representative of enterprises as a whole. It does not measure revenue, token volume, seats, or model requests.
Direct vs. indirect deployment
Naming a provider in a disclosure does not prove whether requests use a direct API or a cloud intermediary. We keep unknown delivery routes separate and do not assign Azure OpenAI, Bedrock, or Vertex usage from a generic cloud-provider relationship.
Embedding and monthly updates
The embeddable image carries its review date and denominator. It changes when a new reviewed snapshot is published. The assembled sample has individual review dates, not a comparable monthly panel; no adoption curve or historical share is inferred.
A public job board supports an ATS observation. A subprocessor disclosure identifies a provider that may process data for particular services. A vendor customer story describes a published relationship. These sources have different scopes and are labeled separately.
Counts cover the records on these pages, not the whole market. No observation in our covered sources does not mean a company does not use a vendor. Source recency and unresolved conflicts affect confidence; observations do not establish spend, renewal timing, or customer churn.