API Evangelist API Evangelist
API Learnings
Toolbox
API Evangelist LLC
API Learnings
Toolbox
API Evangelist LLC

Need help?

Contact us
Kin Lane

Chat with Kin

AI assistant · trained on my blog

83 of the Fortune 100 Have a Developer or API Portal

blog-2026-05 ·
83 of the Fortune 100 Have a Developer or API Portal

I spent some time this week running a complete inventory of public developer, API, and data portals across every Fortune 100 company. Combined apis.yml metadata across the api-evangelist network with web verification of every company that had no clear evidence in the index. The result surprised me a little, as I zoomed out beyond just developer portals.

83 of the Fortune 100 have a public developer, API, or data portal of some kind.

That number is higher than I would have guessed if you had asked me cold. The API economy reaches deeper into corporate America than the “AWS, Stripe, Twilio, Shopify” narrative usually credits it for. But the number is also misleading, because “having a portal” covers a wide range of seriousness — and the gap between the portals that are designed for self-serve developers and the portals that are designed to keep developers out is wider than the headline rate suggests.

You have to wonder what these portals say to agents?

Every company below links to its portal (where one exists) and to its api-evangelist profile where I am tracking the API surface over time.

Big Tech (12)

Universal, mature, and the reference shape for what a developer portal looks like:

Banking and Financial Services (20)

The Open Banking, BaaS, and embedded-finance wave has put a developer portal in front of nearly every major US bank, insurer, and financial-data firm. These programs are larger and more mature than most public commentary reflects at first glance:

Healthcare Payers and Providers (11)

Most of these portals exist because of the CMS Patient Access rule and other interoperability mandates, not because the payer or provider wanted a developer ecosystem. They are FHIR-shaped and often documented through third-party aggregators (1upHealth, Onyx, Particle Health) rather than first-party, but still fit into my strategy at Naftiko:

Retail and Commerce (13)

A mix of self-serve developer programs and supplier or trading-partner portals — the line between them is fuzzier here than in most other sectors:

Airlines and Logistics (5)

Air cargo and shipping have had developer programs longer than most other categories, but the airlines have been a mix bag in my experience:

Automotive (3)

Tesla’s program is the most genuinely public; Ford and GM are partner-oriented but exist and can still reflect what is going on within these manufacturers:

Telecom and Media (5)

One of the oldest developer-program categories, going back to the early part of this century, but may not reflect what the modern definition of API portals look like.:

Energy and Industrial (11)

A mix of true developer portals (Boeing, Deere, Procter & Gamble) and more partner-oriented programs (ExxonMobil, ConocoPhillips, ADM) across these energy companes.

Other F100 With Portals (3)

The 17 Without a Portal

The Fortune 100 companies with no public developer, API, or data portal I could locate — even after web verification — fall into a few clean buckets:

What ties this list together is industry posture, not technology gap. Pharma, defense, energy commodity, and food distribution share a common operational reality — their value flows through long-term contracts, regulated channels, and EDI integrations that pre-date the public API era and that have very little incentives to surface as a developer portal. The customer is not a developer; the customer is a contract counterparty. The integration is not over HTTP; it is over EDI, FIX, FAST, or a long-running B2B exchange. The data is not for public consumption; it is regulated, embargoed, or proprietary in ways that no portal would help with. The questions is, does this need modernization? Or maybe just modern access, and not replacing? IDK yet.

For me, this is not necessarily a failure of API strategy. For these companies, the absence of a public portal is the strategy. The interesting question is whether the agentic AI shift is going to change that — and my early read is that it might, especially for pharma (clinical-trial data exchange) and energy (grid integration, real-time pricing surfaces). Each industry is feeling the AI impact differently, as we’ve been surfacing with Naftiko Signals.

The Spectrum of “Has a Portal”

The 83% headline rate flattens a lot of nuance. When I look at the actual portals, there are at least five distinct shapes hiding inside that bucket–something that reflects my conversation recently with Pronovix.

  1. True public developer portals — self-serve, documented, with API keys you can generate in five minutes. Apple, Google, Microsoft, IBM, Cisco, Tesla, plus banking portals like Capital One and JPMorgan, retailer programs like Walmart and Best Buy. Maybe 35-40 of the 83 land here.
  2. Partner/enterprise gated portals — they look like developer portals but the API keys require a sales conversation, an existing contract, or a partner-program enrollment. State Farm, Centene, Charter Communications, United Airlines NDC, Marathon Petroleum, Costco supplier portal. Maybe 20-25 of the 83.
  3. FHIR / regulatory compliance portals — exist because the law requires them, often documented through third-party aggregators rather than first-party. UnitedHealth, Elevance, Cigna, Humana. The “portal” is sometimes just a landing page directing developers to the FHIR endpoint. 8-10 of the 83.
  4. Supplier and trading partner portals that aren’t really developer programs but are the closest thing the company offers. TJX, Tyson Foods, ConocoPhillips, Costco. 5-7 of the 83. A developer building on top of one of these is mostly building EDI.
  5. Marketing-shaped landing pages — the URL says “developer” but the page is a brochure with a “contact sales” CTA. A handful of entries land here, flagged in the master CSV.

If I tightened the definition to category 1 (true self-serve public developer portals), the Fortune 100 rate would drop to something closer to 35-40%. Still high, but a different number with very different implications. I wanted to widen my portal definition to try and answer agentic questions I have, not necessarily just API questions I have.

What This Means For the API Economy

A few observations.

First, the API economy has reached corporate America more deeply than the public discourse suggests. When the conversation about APIs focuses on Stripe, Twilio, OpenAI, and Anthropic, it is easy to forget that JPMorgan Chase, John Deere, Procter & Gamble, and Boeing all run developer portals. The big-bank developer programs in particular are larger and more mature than most public commentary acknowledges. JPMorgan, Citi, Capital One, and Wells Fargo have been running serious developer programs for years.

Second, the portal isn’t the goal — the consumable surface is. Of the 83 portals, very few are designed for the agent era. Most assume a human developer reading documentation, generating keys, and building integrations. That assumption is going to age poorly fast. The Fortune 100 banks have spent a decade building developer programs that assume a fintech engineer is the consumer. In the next three to five years, the consumer is increasingly going to be an LLM agent acting on behalf of a customer or a co-worker. That is a different design problem, and most of the portals in the 83 are not set up for it.

Third, the gap between “we have a portal” and “we have an agent-consumable API surface” is where the next round of vendor differentiation lives. The MCP wave I have been covering for the last six weeks is exactly this gap, observed at the vendor level. The Fortune 100 are positioned to win or lose the agent-consumption phase based on whether their developer portals evolve into capability surfaces. Right now, most are still developer portals.

Fourth, the 17 without a portal are a leading indicator of an industry’s API readiness. Pharma, defense, energy commodity, and food distribution are the industries with the most regulatory friction and the most legacy B2B integration debt. If they start to ship public developer or data portals over the next two years, it will be because the agentic AI ecosystem made it commercially uncomfortable not to. I will keep watching.

What I’d Like To See Next

A few things I will be building on top of this analysis over the next couple weeks, with the assistance of Claude, and the API Evangelist GitHub organizaiton.

  • A repeat of this analysis for the Fortune 500 (101-500) and Fortune 1000 (501-1000), where I already see the rate dropping to 51% and 41% respectively. The shape of the no-portal majority in those tiers tells a different and more interesting story.
  • A capability inventory of the F100 portals — not just “does it exist” but “what APIs does it actually offer, with what auth model, with what rate limits, with what SDK coverage.” That is a much harder data collection problem, but it is the one that matters for the agent era.
  • An MCP and skill coverage map across the same 83 portals — which of them have shipped an MCP server, which have shipped a skill bundle, which have neither. My early sense is that the answer is “almost none have shipped either, and the gap between portal and MCP is going to be the next ground truth for API maturity at scale.”

The full data, including portal URLs, source classification, and the 905 non-Fortune-100 providers I evaluated, lives on GitHub. I will publish the cleaned-up version of the analysis with the per-portal capability inventory once that work is done.

I have been profiling all of the technology investments these companies have been making, the services they have adopted, as well as the open-source standards and tooling they ar eusing as part of our Naftiko Signals. I am trying to connect the dots between the services these companies produce with the services they consume, from the outside-in. If this data is of interest to you, feel free to reach out, and I’ll share more about what the road map looks, and how we’ll be packaging up our insights as API, MCP, and Agent Skills, reflect the core functionality of Naftiko Capabilities.

#Fortune 100 #API Portals #Developer Portals #API Economy
About this post
Published
Author
Newsletter

Weekly highlights of stories, conversations, and API knowledge delivered Monday mornings.

Naftiko Signals
Naftiko Signals