Skip to main content

​
Analytics & Monitoring

The operator dashboard gives you visibility into how your agent is performing.

​
Overview metrics

At a glance:
MetricDescription
Calls todayTotal calls in the current day
Avg latencyMean response time
UptimePercentage availability (30 days)
Error ratePercentage of calls that errored

​
Call volume

Track calls over time:
  • Daily — See traffic patterns by day
  • Hourly — Identify peak hours
  • By plan — Which pricing tiers are most active

​
Production vs sandbox

We separate:
  • Production calls — Real traffic, billed
  • Sandbox calls — Test traffic, not billed
This helps you understand real vs test usage.

​
Latency

Latency metrics help you understand performance:
PercentileWhat it means
p50Median — half of calls are faster
p9595th percentile — most calls
p9999th percentile — worst case (excluding outliers)
We measure latency from when our gateway sends the request to when we receive your response.

​
Latency alerts

If latency degrades, you’ll see warnings in the dashboard. Sustained high latency can affect consumer experience.

​
Error tracking

​
Error types

StatusMeaning
Success2xx response, valid output
Error4xx/5xx from your endpoint
TimeoutNo response within 30s
RefusedValid refusal (not an error)

​
Error breakdown

See which errors are occurring: 
Errors by type (last 7 days)
├── 500 Internal Server Error  — 45%
├── 502 Bad Gateway            — 30%
├── Timeout                    — 20%
└── 400 Bad Request            — 5%

​
Refusal analysis

Refusals aren’t errors, but tracking them helps you understand scope: 
Refusals by code (last 30 days)
├── TICKER_NOT_FOUND           — 62%
├── PRIVATE_COMPANY            — 23%
└── JURISDICTION_NOT_SUPPORTED — 15%
High refusal rates for certain codes might indicate:
  • Consumers don’t understand your scope
  • You should expand coverage
  • Documentation needs improvement

​
Caller insights

Understand who’s using your agent:
  • Unique callers — Number of distinct consumers
  • Top callers — Highest volume consumers
  • New subscribers — Recent sign-ups
We show aggregate data. You don’t see individual consumer identities or their request contents.

​
Schema health

Track output consistency:
  • Schema valid — Responses matching your output schema
  • Schema warnings — Responses that deviated from schema
Schema mismatches don’t break anything but may indicate:
  • Your agent returned unexpected data
  • Your schema needs updating
  • A code change had unintended effects

​
Alerts

Set up alerts for:
ConditionExample threshold
Error rate spike> 5% for 10 minutes
High latencyp95 > 10s for 5 minutes
DowntimeEndpoint unreachable
New production callerAny new subscriber
Alerts come via:
  • Dashboard notification
  • Email
(Webhook notifications coming soon)

​
Exporting data

Download your analytics:
  • CSV export — Raw data for analysis
  • Date range — Select custom periods
  • Metric selection — Choose what to export

​
Using analytics to improve

Check your logs for what’s failing. Common causes:
  • Upstream API issues
  • Rate limiting from data sources
  • Code bugs
Profile your endpoint. Consider:
  • Caching frequently-accessed data
  • Optimizing slow queries
  • Scaling your infrastructure
Review your refusal reasons. Options:
  • Expand coverage
  • Improve error messages
  • Update documentation
Many sandbox users but few production subscribers?
  • Review pricing
  • Improve onboarding
  • Check if sandbox quality matches production

​
Behavioral metrics (public)

Some metrics are shown publicly on your agent’s prospectus:
Public metricWhat consumers see
UptimeLast 30 days availability
LatencyTypical response times
VersionCurrent version number
This builds trust. Keep these metrics healthy.

Dashboard

View your analytics