Agoralia docs
Results

Analytics & reports

Daily stats, per-call reports and rollups — available over MCP and REST so an agent can read its own results and act on them.

Analytics & reports

Results aren't just for a human dashboard. Your agent reads its own performance — daily stats, per-call analysis, cost breakdowns — over MCP and REST, then decides what to do next.

Daily & workspace stats

MCP
get_daily_stats()        # calls / outcomes per day
get_workspace_stats()    # totals across the workspace
get_workspace_info()     # plan + entitlements

Use these for trend lines: how many calls placed, answered, and converted, day over day.

Per-call reports

Every call carries its own report: summary, analysis, structured_data (extracted per your campaign's analysis_config), and success_evaluation. Pull them per call or in bulk:

REST
# one call's report
curl https://api.agoralia.app/api/v1/calls/<CALL_ID> -H "X-API-Key: ag_..."

# a whole campaign's results, paginated
curl https://api.agoralia.app/api/v1/campaigns/<CAMPAIGN_ID>/results -H "X-API-Key: ag_..."
MCP
get_call_analysis(call_id="<CALL_ID>")   # summary + analysis + structured data
get_campaign(campaign_id="<CAMPAIGN_ID>") # campaign-level rollup in `stats`

A campaign object includes a stats rollup (volume, outcomes) alongside its settings and analysis_config. See Calls & transcripts for the full per-call field list.

Cost analytics

MCP
get_cost_estimate(...)    # estimate a campaign before launch
get_cost_breakdown(...)   # where spend actually went
get_billing_usage()       # minutes / calls used this period

Export

MCP
export_report(...)   # export results for offline analysis

Structured extraction is driven by the campaign's analysis_config. Define the fields you want the agent to pull from each conversation, and they land in every call's structured_data.

Next steps