Blog
Stripe bought the meter. Someone still has to keep the ledger.
Stripe is paying $7.5 billion for OpenRouter, months after Palo Alto bought Portkey. Two acquisitions in one quarter say the layer that decides how to spend AI is now strategic. But notice what neither buyer bought: the evidence.
August 19, 2026 · 4 min read
Stripe is acquiring OpenRouter for about $7.5 billion, a 5.4x markup over the valuation OpenRouter raised at three months earlier. A few weeks before that, Palo Alto Networks bought Portkey. Two acquisitions of the AI-gateway layer in a single quarter, by a payments giant and a security giant. If you had any doubt that deciding how to spend AI is now the valuable layer, the market just removed it twice, and the second time it did so at $7.5 billion.
We think that's the right read. Intelligence stopped being the scarce thing. Deciding how to spend it, which model for which job, at what cost, under what rules, is the scarce thing now. That has been our whole thesis. It's satisfying to watch two of the largest acquirers in tech agree in public.
Now look at which layer each of them actually bought
Stripe did not buy a governance company. They bought the meter: one API to hundreds of models, cost optimization, and, the part that made it a Stripe deal specifically, the billing and settlement problem of who pays whom when a request fans out across a marketplace of model providers. That is a payments problem, which is exactly why a payments company paid up for it.
Palo Alto bought the enterprise-suite version: a gateway folded into a security platform you buy top-down, with the procurement runway to match.
Between them they bought the meter and the enterprise suite. Neither one bought the thing a bank, an insurer, or a regulator actually asks for after the fact: independent, verifiable evidence of what your AI did. A meter tells you what a request cost. It does not tell an auditor, in a form they can check without trusting the vendor, which model handled a customer's data, whether it was screened first, and whether the record was edited after the fact. Metering is a billing artifact. Evidence is a different artifact, and it is the one that clears a review.
Same shade, different layer
There is a tidy stack forming here. Companies bought agents, then bought a layer to govern what the agents can touch. Companies bought models, and a routing layer exists to decide which model gets which job and what it costs. Each acquisition consolidates one of those layers. The layer that keeps consolidating is the one about spending and metering, because that is where the incumbents already live: payments companies meter, security suites gate.
The layer nobody has consolidated is the one above both: the provable record. When intelligence is cheap and interchangeable and flowing through a metered marketplace, the durable asset is not the routing table and not the invoice. It is the signed, tamper-evident account of what actually happened, that your auditor can verify offline, trusting only the math. Routers and meters structurally do not produce it, because producing it was never their job.
That's the layer RemKey is
RemKey is the AI layer you can prove to a regulator, one base-URL swap. It routes each request to the cheapest capable model and proves the downgrade held quality, so it does the meter's job of spending well. But then it does the part the meter doesn't: it screens every call fail-closed, labels every model's jurisdiction so you can govern which ones touch your data, and writes each decision to a hash-chained, Ed25519-signed ledger your auditor verifies offline with an open standalone tool. When the routing layer is a $7.5 billion line item inside a payments company, the evidence layer above it is not a nice-to-have. It's the part that was never for sale, because nobody had built it to sell.
We're glad Stripe and Palo Alto validated the neighborhood. We're building the house on the one lot they didn't buy. Swap the base URL and every call is metered, governed, and provable from the first request.
What the evidence layer looks like under a review How we govern ourselves