rtcStats
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.
AgentCard object — a capabilities object, a declared protocolVersion, and a well-formed skills array.
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://api.rtcstats.com/v1.0
· transport HTTP+JSON
· protocol Check credit quota get_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.
quotacreditsbillingwebrtcList and filter analyzed sessions list_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 (hasCritical, hasHigh, hasMedium, hasLowScore, hasMediumScore, hasHighScore). This is the triage entry point: narrow to the bad calls, then read them.
webrtcsessionstriageobservabilitymonitoringRead a full analyzed session get_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.
webrtcdebuggingroot-causeobservationsexperience-scoreExplain an observation type get_observation_explanation
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.
webrtcobservationsexplanation2026-09-28 from https://api.rtcstats.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.