Account Management

​

Main account workflows

​

What Lives Here

• balance inspection
• usage and activity reporting
• API key lifecycle management

​

What You Can Do

• monitor remaining credits before large jobs or batch runs
• inspect request volume, spend, and top models over time
• split usage by API key for teams, apps, or environments
• create separate keys for production, staging, development, and CI
• apply per-key credit limits as lightweight budget controls

​

Authentication Reminder

Authorization: Bearer YOUR_PROVISIONING_KEY

​

Quick Operational Check

import requests

response = requests.get(
    "https://api.naga.ac/v1/account/balance",
    headers={"Authorization": "Bearer YOUR_PROVISIONING_KEY"},
)
response.raise_for_status()

print(response.json()["balance"])

const response = await fetch('https://api.naga.ac/v1/account/balance', {
  headers: {
    Authorization: 'Bearer YOUR_PROVISIONING_KEY',
  },
});

if (!response.ok) {
  throw new Error(`Request failed: ${response.status}`);
}

const data = await response.json();
console.log(data.balance);

curl https://api.naga.ac/v1/account/balance \
  -H "Authorization: Bearer YOUR_PROVISIONING_KEY"

​

When to use these endpoints

• before running large jobs that depend on paid models
• when you need internal dashboards or billing alerts
• when you want separate keys for production, staging, CI, or customer-specific workloads

​

Main Workflows

​

Balance Monitoring

• stop jobs before credits run out
• alert on low-balance conditions
• integrate billing visibility into internal tooling

​

Activity Analysis

• which models cost the most
• how usage changes day by day
• which API keys or projects are driving spend

​

API Key Management

• production and staging separation
• per-environment blast-radius reduction
• per-key credit limits for budget control
• simpler cost attribution by team or project

​

Related Docs

• API Keys
• Balance and Activity
• Pricing and Billing