Browse documentation
Route account, billing, and API alerts with clear ownership
Notification settings are treated as an operational surface: low balance, key activity, billing changes, API failures, and product updates should route to the right workspace owner.
Your platform
Overview
Read changelog
Follow platform updates
Use the changelog for endpoint, billing, citation, document, and UI behavior changes.
Contact support
Route support questions
Use contact for billing, account, API volume, and integration questions.
internal event{
"type": "low_word_balance",
"workspace_id": "user_workspace",
"words_remaining": 2858,
"action_url": "/dashboard#workspace-billing"
}
Review board
01
Low balance
Warn teams before humanizer or detector requests run out of words.
02
Key events
Surface key creation, revocation, and suspicious authentication failures.
03
Product updates
Developer-facing changes are summarized in the public changelog.
Alert model
Notifications should map to real workflow risk
Balance changes
Notify account owners when remaining words fall below a threshold that could block production jobs.
Key lifecycle
Notify when a new key is created, a key is revoked, or authentication failures spike.
Billing events
Route successful upgrades, failed payments, renewal issues, and portal changes to the workspace owner.
API compatibility
Use changelog entries for endpoint additions, response fields, and documented limit changes.
Notification channels