Organization keys work exactly like personal ones at the model API — same header, same endpoints. What differs is the account they charge and the fact that an owner can issue, retarget and revoke them centrally.
Managing keys
| Method | Path | Role |
|---|---|---|
GET | /api/organization/{id}/tokens | Owner — every key in the org |
POST | /api/organization/{id}/tokens | Owner — issue a key |
PUT | /api/organization/{id}/tokens/{token_id} | Owner — edit limits or assignment |
DELETE | /api/organization/{id}/tokens/{token_id} | Owner — revoke |
GET | /api/organization/{id}/tokens/mine | Member — keys allocated to you |
A key can be assigned to a person, to a team, or to nobody yet — an unassigned key is a useful way to prepare access before you know who will hold it.
curl
curl https://your-instance.com/api/organization/$ORG_ID/tokens \
-H "Authorization: Bearer $CLAWROUTER_ACCESS_TOKEN" \
-H "New-Api-User: $USER_ID" \
-H "Content-Type: application/json" \
-d '{
"name": "platform-shared",
"remain_quota": 5000000,
"model_limits_enabled": true,
"model_limits": "claude-sonnet-5,gpt-5.2"
}'