ID side teams start designing Consent tokens to add to AI API calls.

Today, when a company calls for instance OpenAI or Anthropic, user data is sent to an AI model, but nothing in the request proves what the user actually consented to regarding such data processing.

To address this gap and fix that, ID side teams start designing an "identity-side" solution. Here’s how it could work tomorrow, based on our architecture-layered, machine-readable and enforceable system:
1️⃣ A company integrates an SDK (Web, Backend, or Mobile).
2️⃣ The user sets their AI preferences (training allowed, retention rules, etc.).
3️⃣ Before every AI API call, the SDK retrieves those preferences.
4️⃣ A signed consent token is automatically injected into the request.

The added value is simple: no manual work for developers after integration & no separate compliance workflow -all happening at the infrastructure layer.

A tool sitting directly between one's system and an AI provider to ensure every request carries automatically verifiable human consent.