Applications

Create multiple applications within your tenant to get per-app cost breakdowns, separate API keys, and granular savings attribution. Available on the Scale plan and above.

ℹPlan limits

Sandbox: 1 app, 1 key. Builder: 2 apps, 3 keys. Scale+: Unlimited apps and keys.

Why use multiple applications?

Separate cost tracking per product (e.g., "Support Bot" vs "Research Agent")
Isolate API keys — revoke one app's key without affecting others
Per-app savings charts in the dashboard
Assign budgets to specific applications

Create an application

bash

curl -X POST https://api.laghav.ai/api/applications \
  -H "Authorization: Bearer lgh_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"name": "Support Bot"}'
# Response:
# {
#   "id": "app_xyz789",
#   "name": "Support Bot",
#   "api_key": "lgh_live_xxxx",   <- store this, shown once
#   "created_at": "2025-06-01T14:00:00Z"
# }

List applications

bash

curl https://api.laghav.ai/api/applications \
  -H "Authorization: Bearer lgh_live_xxx"
# {
#   "applications": [
#     {
#       "id": "app_abc123",
#       "name": "FARA Agent",
#       "calls_today": 12400,
#       "compression_avg": 72,
#       "quality_avg": 96,
#       "saved_usd_today": 88.50,
#       "status": "active"
#     }
#   ]
# }

Using app-specific API keys

app_keys.py

# Create a key tied to a specific app
# POST /api/keys  { "name": "Support Bot Key", "app_id": "app_xyz789" }
 
# Use the app-specific key in that app's SDK client
support_client = LaghavClient(api_key="lgh_live_support_bot_key")
agent_client   = LaghavClient(api_key="lgh_live_agent_key")
 
# Each client's calls are attributed to its respective app in the dashboard

✦Cost attribution in the dashboard

The dashboard shows per-application breakdowns: calls, tokens saved, cost saved, and quality avg. Use this to identify which apps have the highest ROI and where to focus optimization.

Budget Controls

Ready to start saving?

Free tier · No credit card · Live in 10 minutes.

Start free →Try the playground