Twitter/X

Clement Delangue (2026-08-05) asserts APIs (what Anthropic, OpenAI and others…

2026-08-05 · 13:18 UTC ·@ClementDelangue ·2 min read

Brief

Clement Delangue argues (2026-08-05) that APIs should be regulated differently from open model weights: weights are the raw “steel” of AI, APIs are the engine suppliers, and apps are the cars where harm occurs. He urges regulators to keep research open, hold API providers to transparency, security and accountability, and push legal obligations to the deployment layer, citing labs, startups and safety researchers as examples.

Why it matters

Clement Delangue (2026-08-05) asserts APIs (what Anthropic, OpenAI and others provide) should be treated differently than open model weights; he calls weights the “steel” of AI and warns that restricting weights would slow downstream innovation and concentrate power.

Key details

  • He lays out three layers—model weights (research), APIs (commercial service) and apps (deployment)—and argues regulation should target where risk materializes: require API providers to deliver transparency, security standards and accountability, and impose obligations at the deployment/app layer.
  • Delangue cites concrete benefits of open weights—labs fine-tuning models for rare diseases, startups serving languages ignored by big providers, and safety researchers auditing models—and insists apps (medical assistants, hiring tools, financial advisors) must comply with existing health/finance/employment/consumer protection rules; he closes by praising @realDonaldTrump, @DavidSacks and @mkratsios47.
Source evidence

Some people are surprised that APIs (aka what Anthropic, OpenAI, and others provide) are treated differently than open weights in the new AI model framework.

I'm not surprised at all, and it's actually very good policy. Let me explain:

Model weights, APIs, and apps are three very different layers of the stack. Treating them the same would be a recipe for bad regulation.

Think about how we handle cars. We don't regulate steel, we crash-test cars. Nobody asks a steel mill to guarantee that nothing dangerous will ever be built with its steel. Obligations sit with the carmaker and rules of the road with the driver, because that's where risk becomes real and where someone can actually act on it.

Model weights are the steel of AI. They're raw research output, closer to science than product: no user, no interface, no deployment. They don't do anything on their own. And because everything else is built on top of them, this is the layer where regulation does the most damage. Restrict weights and you slow down all progress downstream, and you prevent countless positive use cases from ever emerging: the lab fine-tuning an open model for rare diseases, the startup serving a language big providers ignore, the safety researchers who can only audit models because the weights are open. You don't reduce risk, you just kill open source and concentrate power in a few big labs.

APIs are the middle layer, the parts and engine suppliers of AI: a commercial service where a provider serves a model at scale. Here you have a business relationship, terms of service, the ability to monitor for abuse. It makes sense to expect transparency, security standards, and accountability from providers at this layer, because they can actually enforce things.

Apps are the car on the road: where AI meets the real world. A medical assistant, a hiring tool, a companion for kids, a financial advisor. This is where concrete harm can happen, and conveniently, it's where we already have decades of regulation. Health, finance, employment, consumer protection. An AI hiring tool should comply with employment law whether it's powered by an open model, an API, or a spreadsheet.

The principle is simple: regulate at the layer where risk actually materializes and where actors can act on it. Push obligations to the deployment layer, keep the research layer open. We don't regulate steel, we crash-test cars. Well done @realDonaldTrump @DavidSacks @mkratsios47!