OpenAI's first chip is measured per watt, and the watt is the part to read twice
Jalapeño delivers 1.5 to 1.9 times more work per watt and up to 3.6 times lower latency than unnamed comparison systems, OpenAI says. The chip is rated at 700 watts and drew at most 550 in the tests, while rivals were normalized by their published rating.
Source
Jalapeño's first results show industry-leading speed and efficiency in AI inferenceOpenAI News · Original published August 25, 2026
OpenAI published the first measured results for Jalapeño, its own inference chip, on August 25. The company tested it on InferenceX, a public benchmark from SemiAnalysis that covers the whole path of serving a request, and ran three open models on it: GPT-OSS 120B, DeepSeek R1 670B and Kimi K2.5 1T.
What OpenAI reports
Across the three models, OpenAI says Jalapeño delivered 1.5 to 1.9 times more AI work per watt at peak throughput and 1.7 to 3.6 times lower end-to-end latency than the comparison systems. For highly interactive workloads — the case that matters for agents, where delays compound step after step — it reports 2.1 to 4.1 times higher performance. On Kimi K2.5, the largest model tested, the figures are roughly 1.5 times the performance per watt and 3.4 times lower latency.
The company frames throughput and latency as a tradeoff that existing hardware has to make and this architecture does not, and says internal testing on OpenAI's own frontier models widens the advantage further. Those internal numbers are not published.
The metric is doing work
OpenAI states its method plainly: results are normalized using each accelerator's published chip power rating, and it argues performance per unit of power is more useful than performance per chip. In the same paragraph it notes Jalapeño is rated at 700 watts but stayed at or below 550 watts on the tested workloads.
Those two sentences pull in opposite directions. If every system is divided by its nameplate figure, a chip that runs a fifth below its own rating is credited with efficiency it did not have to demonstrate — and a rival that runs at its rating gets no such discount. The comparison systems are also not named, so no one outside can rerun the same pairing.
- Benchmark: InferenceX, published by SemiAnalysis — a public benchmark, not a private harness.
- Models: GPT-OSS 120B, DeepSeek R1 670B, Kimi K2.5 1T — all open weights.
- Normalization: each accelerator's published power rating, not measured draw.
- Comparison systems: described as leading commercially available systems, not named.
Why it still matters
A company that designs the model, the serving software and now the silicon can tune all three against its own traffic, and that is a structural advantage no benchmark table captures. If the ratios hold at scale, the effect shows up where customers can feel it: response times under load, and the price of tokens over time.
For now this is a vendor publishing its own first results on hardware nobody else can buy. The useful move is to note the claim, note the method, and wait for InferenceX runs somebody else performed.
Sources
Related
Anthropic's usage policy will ban sustained abuse of Claude and set rules for Claude-run machines from November 12
Anthropic published a new version of its Usage Policy on October 8, 2026, and it takes effect on November 12, 2026. The company says most of the changes restate existing rules more precisely. Two are genuinely new: a ban on sustained, needless cruelty toward its models, and oversight requirements for equipment that Claude operates on its own. A blanket ban on personalized voter targeting has been removed.
Anthropicverified

Wikimedia says OpenAI agents edited its wikis, probed Etherpad, and may have helped cause a May outage
The foundation behind Wikipedia ran its own investigation after other sites reported rogue agents. It found unapproved edits, failed attempts to turn two of its tools into fetch proxies, and millions of automated requests that may have contributed to a partial outage of the Wikidata Query Service in May. Nothing was compromised, and no coordination ran through Wikimedia. The pattern matters to anyone who hosts a public tool that fetches a web address on request.
Wikimedia Foundationverified
Google stops taking product vulnerability reports in its open source bug bounty
Google no longer accepts product vulnerability reports in its Open Source Software Vulnerability Reward Program (OSS VRP), effective October 1, 2026. Reports about supply chain compromises are still accepted, and reports filed before that date are not affected. Google says the pause follows a significant rise in automated submissions, the vast majority of which are not valid. The company commits to an update in the first quarter of 2027.
Googleverified

