Providers

Resellers

Tag requests with your end customer's id so moderation suspensions land on that customer, not your organization.

You are a reseller when requests from many of your own customers reach us through your API keys: an app, an agent platform or another gateway. With reseller attribution, you tag each request with your end customer's safety_identifier, and a moderation suspension on an uncensored model applies to that customer only.

Getting attribution

Attribution is granted after a short review. Email founders@experientiallabs.ai with your organization ID, what you resell, roughly how many end customers you serve and how you verify them. Until it is granted, your organization is treated as one customer whatever identifiers you send.

At a glance
Fieldsafety_identifier (else user)
SurfacesChat Completions, Responses
Forwarded to providerNever
In usage exportattribution_label

Tagging requests

Set safety_identifier to a stable, opaque ID for the end customer, such as a hash of your internal user ID. Never send an email or a name. We keep it with the request for attribution and usage reporting; moderation keeps only a SHA-256 of it.

curl https://api.experientiallabs.ai/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "glm-5.3-uncensored",
    "safety_identifier": "cust_7f3a9c",
    "messages": [{"role": "user", "content": "hello"}]
  }'

How suspensions are attributed

SituationWho is suspendedResponse
One end customer is flagged repeatedlyThat customer, from uncensored models only403 uncensored_end_user_suspended
A flagged request has no identifierYour organization403 uncensored_access_suspended
Flags come from many distinct end customersYour organization403 uncensored_access_suspended

Each history escalates on its own: 1 hour, 24 hours, 7 days, 30 days, then permanent. Your admins get an email with the customer's hashed reference and the end time. When you see uncensored_end_user_suspended, stop that customer's uncensored requests; a new identifier for the same customer counts toward the organization limit.

Your obligations
One identifier per end customer, stableRequired
No personal data in itRequired
No new identifiers to evade a suspensionRequired
Act on suspensions we reportRequired

Appeal an end-customer suspension by email with the identifier and a request ID.