Skip to main content
Track your platform usage in real-time and understand costs associated with your agents, gateways, and capabilities.

​
Usage Dashboard

​
Accessing Usage

  1. Go to Account > Usage
  2. View metrics for:
    • Tokens consumed (input + output)
    • Cost per model
    • Request counts
    • Error rates
    • Time period selection (Today, Week, Month, Custom)

​
Key Metrics

MetricDescription
TokensTotal input + output tokens across all models
CostCalculated based on model pricing and region
RequestsNumber of API calls and tool executions
ErrorsFailed requests and their error types
LatencyAverage response time (p50, p95, p99)

​
Token Accounting

Tokens are the primary unit of usage and cost calculation.

​
Token Types

Input Tokens:
  • Prompt text you send to the model
  • System prompt
  • Context windows and memory
  • Tool descriptions
  • Prior conversation history
Output Tokens:
  • Model response text
  • Tool execution results
  • Streaming overhead

​
Token Pricing

Pricing varies by model. For current rates, see Pricing.

​
Cost Optimization

​
Use Smart Routing

Let Noorle optimize model selection automatically. Smart Routing analyzes complexity and picks the right model: 
{
  "routing_strategy": {
    "strategy": "smart"
  }
}

​
Pair Primary + Budget Model

Cheap model for simple tasks, expensive model for complex ones: 
{
  "model_name": "gpt-4o",
  "budget_model": "gpt-4o-mini"
}
Budget model typically saves 50-80% on simple requests.

​
Optimize System Prompts

Shorter system prompts = fewer input tokens: Verbose (high cost): 
You are an AI assistant. You should be helpful, harmless, and honest.
You should always provide detailed explanations...
[continues for 2KB]
Concise (low cost): 
Helpful AI assistant. Provide clear, brief responses.

​
Configure Memory Settings

Reduce context window size for cheaper operations:
  1. Agent Settings > Memory Configuration
  2. Set working_memory_size to minimum needed
  3. Reduce summary_token_threshold
  4. Set summary_message_threshold to trigger summaries earlier

​
Batch Requests

Process multiple items in one request instead of individual calls: Expensive (separate calls): 
3 API calls × 1000 tokens each = 3000 tokens
Efficient (batch): 
1 API call × 2500 tokens = 2500 tokens saved

​
Use Caching and Memory

Leverage conversation memory to avoid re-processing:
  • Enable agent memory (3-tier system)
  • Reuse context across requests
  • Let platform manage summarization

​
Platform Limits

LimitValueNotes
Upload Size20MBMaximum request payload
MCP Request Timeout240 secondsPer gateway request
For plan-specific limits and quotas, see Pricing.
Contact sales for custom enterprise limits.

​
Hitting Limits

If you hit a rate limit: 
HTTP 429 Too Many Requests
Response includes: 
{
  "error": "rate_limit_exceeded",
  "retry_after_seconds": 60
}
Handling:
  • Implement exponential backoff
  • Batch requests
  • Request custom limits

​
Usage Breakdown by Resource

​
By Agent

  1. Go to Agents > Select Agent
  2. Click Usage tab
  3. See tokens and cost for this agent only

​
By Gateway

  1. Go to Gateways > Select Gateway
  2. Click Usage tab
  3. See tokens and cost for this gateway only

​
By Model

  1. Go to Account > Usage
  2. View “By Model” table
  3. See which models are most expensive

​
By Capability

  1. Go to Account > Usage
  2. View “By Capability” table
  3. See cost of each capability (Web Search, Code Runner, etc.)

​
Capability Limits Reference

LimitValueNotes
Timeout30 secondsPer request
Max Results10Per query
Max Retries3Automatic
Optimization Tips: Use specific queries to reduce result processing. Cache recurring searches in Files capability.

​
Browser

LimitValueNotes
Timeout30 secondsConfigurable
Default Viewport1280 × 720Configurable
JavaScriptEnabledFully renders dynamic content
Optimization Tips: Use text extraction instead of screenshots when you only need content. Set appropriate timeouts for slow pages.

​
Code Runner

LimitValueNotes
Timeout30 secondsMaximum execution time
Memory128MBPer execution (configurable up to 512MB)
CPU Time~100msMaximum CPU time
Code Size10KBMaximum code length
Output Size1MBConsole output
NetworkDisabledNo HTTP requests
File I/ODisabledNo file read/write
Optimization Tips: Keep executions under 100ms CPU time. Process large datasets in chunks. Use Sandbox for anything needing external packages or network access.

​
Sandbox

LimitValueNotes
SizesXS to XL5 predefined tiers
vCPU Range0.25 – 4.0Based on size
Memory Range1 GB – 12 GBBased on size
Disk Range4 GB – 20 GBBased on size
Command Timeout5 min default, 30 min maxConfigurable
Max Lifetime60 minutesAuto-terminates
Idle Timeout20 minAuto-terminates
Containers per Session1One active at a time
NetworkOutbound onlyNo inbound connections
Optimization Tips: Start with the smallest size (XS) and scale up as needed. Use Code Runner for simple operations that don’t need packages. Sandboxes auto-terminate after 20 min idle to save costs.

​
HTTP Client

LimitValueNotes
Request Body2MBMaximum size
Response Body2MBMaximum size
Timeout30s defaultMin 1s, max 300s
Rate Limit1,000/minPer user
Max Redirects10Per request chain
Optimization Tips: Implement retry logic with exponential backoff. Compress large payloads. Use connection pooling for repeated calls to the same host.

​
Files

LimitValueNotes
Per-File Size10MBAll scopes
Files per Scope100Per scope
Agent Home Storage50MBPersistent agent storage
Optimization Tips: Use session-scoped files for temporary processing. Only persist results to agent home when needed. Clean up unneeded files to stay within limits.

​
Knowledge Retrieval

LimitValueNotes
Query Length500 charsSearch query max
Results per Search100Maximum
Document Size10MBPer document
Index Size10GBPer knowledge base
Concurrent Searches100/secPer knowledge base
Optimization Tips: Pre-filter with metadata before searching. Use appropriate chunk sizes for your documents. Cache frequent queries.

​
Computer

LimitValueNotes
Sizesx2 to x325 predefined tiers
vCPU Range2 – 16Based on size
RAM Range2 GB – 32 GBBased on size
Disk Range40 GB – 360 GBBased on size
Default Sizex43 vCPU, 4 GB RAM, 80 GB disk
SSH Timeout30 secondsPer command
Browser Max Tabs5Per session
Browser Max Download50 MBPer file
Snapshot Elements500Truncated if exceeded
Optimization Tips: Start with x4 (default) and scale up for memory-intensive or multi-process workloads. Enable browser subsystem only if needed. Agent-only — not available on MCP gateways.

​
Plugins (WebAssembly)

LimitValueNotes
Memory128MB default, 512MB maxPer invocation
CPU Time100ms maxPer request
Timeout30s default, 120s maxConfigurable
Module Size10MBCompressed npack file
Optimization Tips: Configure memory limits based on your workload (up to 512MB max). Set appropriate timeouts (up to 120s max). Keep module size small for faster deployment.

​
Pricing and Billing

For current pricing details, plan comparisons, and billing information, see Pricing.

​
Alerts and Budgets

​
Budget Alerts

Set spending threshold to receive notifications:
  1. Go to Account > Billing > Budget Alerts
  2. Click Create Alert
  3. Set threshold amount
  4. Choose notification method (email, webhook)
  5. Click Save
You’ll be notified when spending reaches the threshold.

​
Usage Alerts

Get notified when you approach limits:
  1. Go to Account > Usage > Alerts
  2. Toggle the limits you want to monitor:
    • Daily API calls
    • Storage usage
    • Token consumption
  3. Set notification threshold
  4. Click Save

​
Enterprise Limits

For enterprise plans with custom limits, contact sales@noorle.com or see Pricing.

​
Troubleshooting

​
High Unexpected Cost

Check:
  1. Go to Usage dashboard
  2. Filter by time period (daily, hourly)
  3. Identify which resource is expensive
  4. Check token breakdown by model
Common causes:
  • Large system prompt
  • Expensive model selected
  • Budget model not triggering
  • Streaming overhead
  • Knowledge base queries with large documents

​
Hitting Rate Limit

Solutions:
  1. Implement exponential backoff
  2. Batch requests
  3. Reduce concurrent requests
  4. Upgrade plan
  5. Contact support for custom limits

​
Usage Not Updating

Give it time: Usage updates every 5-15 minutes. Check again in a few minutes. Force refresh: Go to different tab and return.

​
API Access

Query usage programmatically: 
# Get usage statistics
curl https://api.noorle.com/v1/usage/summary \
  -H "X-API-Key: ak-{your_key}"

# Get detailed usage
curl https://api.noorle.com/v1/usage/detailed?period=month \
  -H "X-API-Key: ak-{your_key}"

# Get resource-specific usage
curl https://api.noorle.com/v1/agents/{agent_id}/usage \
  -H "X-API-Key: ak-{your_key}"

​
Next Steps