Accounts and API keys
API keys are shown once, stored encrypted, and can be split by member, project, or tool.
- Encrypted API key storage
- Per-key RPM, daily budget, IP, and Origin controls
- Instant revocation for abnormal keys
← Back to home
Trust / Security / Operations
AICodeDog Trust Center
AICodeDog turns the fragile parts of an AI relay into verifiable systems: encrypted keys, signed payments, real usage billing, ledgers, webhooks, backups, and operations checks.
Payments and balance
Top-up callbacks are signed, amount-checked, and idempotent. Refunds create traceable ledger rows.
- ZPAY / UPay / Stripe support
- Paid orders create balance ledger entries
- Duplicate callbacks do not double-credit
Billing and audit
Only successful billable upstream usage deducts balance. Failed calls are visible for diagnostics but not charged.
- Usage records include model, tokens, cost, and latency
- Insufficient balance blocks non-streaming calls
- Low-balance Webhook/email alerts
Operations
The operations console tracks missing ledgers, negative balances, high-cost models, payment exceptions, and backup status.
- Public status page
- Backup restore drills
- Real user path E2E
FAQ
Are failed requests billed?+
No. Only successful billable model usage deducts balance.
Can payment notifications be forged?+
Callbacks are signature-verified, amount-checked, and handled idempotently.
Can I use OEM or source delivery?+
Yes. Branding, sub-tenants, source delivery, and managed setup are supported.