Beta
Safety and controls
Scoped keys, approvals, spend caps, rate limits, an audit log and data retention on every call.
Screenshot placeholderAPI keys with scopes (keys masked)
product-safetyHow it works
- 1
Limit the key
Give each key only the scopes it needs. Rotate it at any time.
- 2
Approve writes
Write actions wait until someone approves them.
- 3
Watch and keep records
Spend caps and rate limits stop runaway use. Every call goes to the audit log.
Try it
Replace $SETU_API_KEY with a key from the Setu console.
Approve a waiting action
# Approve (or deny) a write action that is waiting.
curl https://setu.supremeai.services/api/setu/v1/approvals/$APPROVAL_ID \
-H "Authorization: Bearer $SETU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "decision": "approve", "reason": "Checked the draft" }'What it does
- Scoped, rotatable keys stored only as a hash.
- Approvals for write actions.
- Spend caps, rate limits, audit export and retention.
- Let an agent act for users without giving it unlimited power.
- Give a read-only key to a dashboard.
Limits and status
Beta- Keys are stored only as a hash. Read-only keys start with sup_ro_.
- The audit log can be exported.
- Not yet: An IP allow-list per key.
Status last checked 2026-10-21.
Questions
What happens when a limit is hit?
The call is refused with 429 and a Retry-After header, or stops at the spend cap. Nothing runs past the limit.