Skip to main content
Administrative account workflows live under /v1/account/* and require a provisioning key rather than a standard inference key. These endpoints are the operational layer for cost control, usage analysis, and key management across projects or environments.

​
Main account workflows

WorkflowEndpoint
Check balanceGET /v1/account/balance
Review activityGET /v1/account/activity
List or create API keysGET /v1/account/keys, POST /v1/account/keys
Inspect, update, or delete one keyGET, PATCH, DELETE /v1/account/keys/{key_id}

​
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

API Keys

Create, rotate, limit, and organize keys by environment or team.

Balance and Activity

Check credits, usage trends, and model-level spend.

Pricing and Billing

Review how paid model access and account balance work.

​
Authentication Reminder

Use: 
Authorization: Bearer YOUR_PROVISIONING_KEY
You can obtain the provisioning key from the NagaAI Dashboard.

​
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"])
Provisioning keys are more privileged than standard inference keys. Store them separately and never embed them in client-side applications.

​
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

Use balance checks when you need to:
  • stop jobs before credits run out
  • alert on low-balance conditions
  • integrate billing visibility into internal tooling

​
Activity Analysis

Activity reports help you answer:
  • which models cost the most
  • how usage changes day by day
  • which API keys or projects are driving spend

​
API Key Management

Use multiple API keys when you want:
  • production and staging separation
  • per-environment blast-radius reduction
  • per-key credit limits for budget control
  • simpler cost attribution by team or project