rtcStats website screenshot

rtcStats

SaaS for developers to troubleshoot and monitor WebRTC applications. Users upload webrtc-internals/rtcstats dumps or stream stats to receive metrics, Observations, Deductions, an Experience Score, and an AI root-cause summary. Offers a REST API, a hosted MCP server, and an open-source collection SDK/collector.

rtcStats publishes 2 API contracts indexed on the APIs.io network. Tagged areas include WebRTC, Observability, Monitoring, Debugging, and Real-Time Communication.

The rtcStats catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

rtcStats’ developer surface includes sandbox, authentication, changelog, documentation, API reference, getting-started guide, support, and 69 more developer resources.

66.8/100 exemplar ▬ flat Agent 48/100 agent ready Front door AI 2/6 trace Heartbeat 88/100 alive open core · MIT Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessFreemiumSelf serve⚡ Free to try
2 published contracts 1 MCP Servers 4 Agent Skills
WebRTCObservabilityMonitoringDebuggingReal-Time CommunicationVideoVoiceArtificial IntelligenceMCPDeveloper Tools

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

SaaS Platform Operations Management
BC-4220
rtcStats API
POST /v1.0/analyze GET /v1.0/observations

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for rtcStats It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/rtcstats/"><img src="https://apis.io/badge/rtcstats/card.svg" alt="rtcStats on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
  • Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/rtcstats/apis.yml: open an issue on github.com/api-evangelist/rtcstats to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)
measured — observed by APIs.io (conformant)
measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

rtcStats API

The rtcStats API API from rtcStats — 8 operation(s) for rtcstats api.

rtcStats MCP Server

Hosted Model Context Protocol server over Streamable HTTP, so coding agents can query analyzed WebRTC sessions. Tools get_quota, list_sessions, get_session and get_observation_e...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

rtcStats rtcStats API API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

rtcStats MCP Server

rtcStats operates a first-party hosted MCP server over Streamable HTTP at https://api.rtcstats.com/v1.0/mcp. It is stateless JSON-RPC 2.0 and is also declared in the OpenAPI as ...

MCP SERVER

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

rtcStats API pricing

Prices published by rtcStats, read 2026-10-28 from rtcstats.com/pricing.

PlanPrice
Free $0/month
Includes: 3 team members, 10 credits, 1 month retention; first month at full Developer-level analysis
Developer $199/month
Includes: 10 team members, 500 credits, 3 months retention, API and MCP access
Enterprise $999/month
Includes: 50 team members, 5,000 credits, 3 months retention, whitelabel sharing, embeddable viewer, 3rd party

Plan details, limits and sources →

Rate limits

Rate-limit details →

Billed by: subscription · FinOps profile →

Pricing Plans 3

Published pricing tiers and plan structures.

Rtcstats Plans

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Rtcstats Rate Limits

3 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Rtcstats Context

13 classes · 83 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

rtcStats API Rules

16 rules · 14 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Rtcstats Api Overlay

12 actions · update · rtcstats-api-openapi.yml

DERIVED

JSON Schema 5

Standalone JSON Schema definitions for this provider's data models.

AnalyzeResponseData

33 properties

JSON SCHEMA

EnrichResponse

3 properties

JSON SCHEMA

ObservationTypesResponse

2 properties

JSON SCHEMA

QuotaResponse

4 properties

JSON SCHEMA

SessionsListResponse

2 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Rtcstats Authentication

http · 1 scheme

SECURITY

Rtcstats Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Rtcstats Vulnerability Disclosure

security.txt · contact published

SECURITY

Rtcstats Trust Center

SOC 2, ISO 27001

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Rtcstats Agentic Access

9 operations · 5 acting

9 operations · 5 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 4

Reference material describing how the API behaves

Agent Surfaces 7

MCP servers, agent skills, and machine-readable catalogs

Scroll for all 7

Design & Contract 13

Pagination, idempotency, versioning, errors, and events

Scroll for all 13

Build 7

SDKs, sample code, and the tooling you integrate with

Scroll for all 7

Access & Security 9

Authentication, authorization, and security posture

Scroll for all 9

Operate 10

Status, limits, changes, and where to get help

Scroll for all 10

Commercial 8

Pricing, plans, and the legal terms of use

Scroll for all 8

Company 2

The organization behind the API

Other 12

Properties that don't map to a standard resource type

Scroll for all 12

Source (apis.yml)

apis.yml Raw ↑
name: rtcStats
description: SaaS for developers to troubleshoot and monitor WebRTC applications. Users upload webrtc-internals/rtcstats dumps
  or stream stats to receive metrics, Observations, Deductions, an Experience Score, and an AI root-cause summary. Offers
  a REST API, a hosted MCP server, and an open-source collection SDK/collector.
url: https://raw.githubusercontent.com/api-evangelist/rtcstats/refs/heads/main/apis.yml
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
created: '2026-08-09'
modified: '2026-09-16'
specificationVersion: '0.23'
tags:
- WebRTC
- Observability
- Monitoring
- Debugging
- Real-Time Communication
- Video
- Voice
- Artificial Intelligence
- MCP
- Developer Tools
tags_raw:
- webrtc
- observability
- monitoring
- debugging
- real-time-communications
- video
- voice
- ai
- mcp
- developer-tools
maintainers:
- FN: rtcStats
  url: https://rtcstats.com
  email: support@rtcstats.com
image: https://rtcstats.com/opengraph-image.png
common:
- type: FinOps
  url: finops/rtcstats-finops.yml
- type: IntegrationEdges
  url: integrations/rtcstats-integration-edges.yml
- type: CapabilityMap
  url: capabilities/rtcstats-capability-edges.yml
  name: rtcStats Business Capability Map
- type: AgenticAccess
  url: https://rtcstats.com/schemas/agentic-access.yml
- type: AgentSkill
  url: https://rtcstats.com/.well-known/agent-skills/rtcstats/SKILL.md
- type: Plans
  url: plans/rtcstats-plans-pricing.yml
- type: Spectral
  url: rules/rtcstats-rules.yml
- type: JSONLD
  url: json-ld/rtcstats-context.jsonld
- type: Vocabulary
  url: vocabulary/rtcstats-vocabulary.yml
- type: Sandbox
  url: sandbox/rtcstats-sandbox.yml
- type: Compliance
  url: https://rtcstats.com/trust
- type: Security
  url: https://rtcstats.com/trust
- type: Deprecation
  url: lifecycle/rtcstats-lifecycle.yml
- type: AgentCard
  url: a2a/rtcstats-a2a.yml
- type: Hosts
  url: hosts/rtcstats-hosts.yml
- type: Vendors
  url: vendors/rtcstats-vendors.yml
- type: TrustCenter
  url: security/rtcstats-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/rtcstats-vulnerability-disclosure.yml
- type: Website
  url: https://www.rtcstats.com/
- type: IssueTracker
  url: https://github.com/rtcstats/rtcstats/issues
- type: Releases
  url: https://github.com/rtcstats/rtcstats/releases
- type: License
  name: MIT
  url: https://github.com/rtcstats/rtcstats/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/rtcstats-agentic-access.yml
- type: DomainSecurity
  url: security/rtcstats-domain-security.yml
- type: Authentication
  url: authentication/rtcstats-authentication.yml
- type: Packages
  url: packages/rtcstats-packages.yml
- type: SDKs
  url: packages/rtcstats-packages.yml
- type: MCPServer
  url: mcp/rtcstats-mcp.yml
- type: ToolCrosswalk
  url: mcp/rtcstats-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/rtcstats-llms.txt
- type: Overlay
  url: overlays/rtcstats-api-overlay.yaml
- type: Conformance
  url: conformance/rtcstats-conformance.yml
- type: ErrorCatalog
  url: errors/rtcstats-problem-types.yml
- type: Lifecycle
  url: lifecycle/rtcstats-lifecycle.yml
- type: Conventions
  url: conventions/rtcstats-conventions.yml
- type: ChangeLog
  url: changelog/rtcstats-changelog.yml
- type: Components
  url: components/rtcstats-components.yml
- type: DataModel
  url: data-model/rtcstats-data-model.yml
- type: RateLimits
  url: rate-limits/rtcstats-rate-limits.yml
- type: Plans
  url: plans/rtcstats-plans.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DeveloperPortal
  url: https://rtcstats.com/api-docs
- type: Documentation
  url: https://rtcstats.com/kb
- type: APIReference
  url: https://rtcstats.com/api-docs.md
- type: GettingStarted
  url: https://rtcstats.com/kb/getting-started
- type: Support
  url: https://rtcstats.com/support
- type: Blog
  url: https://rtcstats.com/blog
- type: ChangeLog
  url: https://rtcstats.com/blog/category/release
- type: GitHubOrganization
  url: https://github.com/rtcstats
- type: SourceCode
  url: https://github.com/rtcstats/rtcstats
- type: Pricing
  url: https://rtcstats.com/pricing
- type: SignUp
  url: https://rtcstats.com/register
- type: TermsOfService
  url: https://rtcstats.com/tos
- type: PrivacyPolicy
  url: https://rtcstats.com/privacy
- type: APIsJSON
  name: APIs.json index (provider-hosted)
  url: https://rtcstats.com/apis.yml
- type: WellKnown
  url: well-known/rtcstats-well-known.yml
- type: APICatalog
  url: https://rtcstats.com/.well-known/api-catalog
- type: APICatalog
  url: https://api.rtcstats.com/.well-known/api-catalog
- type: AgentCard
  url: https://rtcstats.com/.well-known/agent-card.json
- type: AgentCard
  url: https://api.rtcstats.com/.well-known/agent-card.json
- type: SecurityTxt
  url: https://rtcstats.com/.well-known/security.txt
- type: SecurityTxt
  url: https://api.rtcstats.com/.well-known/security.txt
- type: Deprecation
  url: https://rtcstats.com/deprecation
- type: ChangeLog
  url: https://rtcstats.com/changelog
- type: Compliance
  url: https://rtcstats.com/compliance
- type: Subprocessors
  url: https://rtcstats.com/compliance
- type: FinOps
  url: https://rtcstats.com/finops.json
- type: RateLimits
  url: https://rtcstats.com/api-docs#rate-limits
- type: PostmanCollection
  url: https://rtcstats.com/schemas/rtcstats.postman_collection.json
- type: SpectralRuleset
  url: https://rtcstats.com/schemas/spectral.yml
- type: Vocabulary
  url: https://rtcstats.com/schemas/vocabulary.json
- type: JSONSchema
  url: https://rtcstats.com/schemas/index.json
- type: JSONLD
  url: https://rtcstats.com/schemas/context.jsonld
- type: Conformance
  url: https://rtcstats.com/schemas/conformance.yml
- type: Overlay
  url: https://rtcstats.com/schemas/overlay.yaml
- type: Documentation
  name: Open-source collector (rtcstats-js, rtcstats-server)
  url: https://rtcstats.com/kb/open-source
apis:
- aid: rtcstats:rtcstats-rtcstats-api-api
  name: rtcStats API
  description: The rtcStats API API from rtcStats — 8 operation(s) for rtcstats api.
  humanURL: https://rtcstats.com/api-docs
  baseURL: https://api.rtcstats.com/v1.0
  tags:
  - rtcStats API
  properties:
  - type: OpenAPI
    url: openapi/rtcstats-rtcstats-api-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted)
    url: https://rtcstats.com/api/openapi
  - type: Authentication
    url: https://rtcstats.com/api-docs#authentication
  - type: Documentation
    url: https://rtcstats.com/api-docs
  - type: Documentation
    url: https://rtcstats.com/api-docs.md
  - type: LLMsTxt
    url: https://rtcstats.com/llms.txt
  - type: APIReference
    url: https://rtcstats.com/api-docs.md
  - type: GettingStarted
    url: https://rtcstats.com/kb/getting-started
  - type: ToolCrosswalk
    url: mcp/rtcstats-tool-crosswalk.yml
  - type: LLMsTxt
    url: llms/rtcstats-llms.txt
  - type: Authentication
    url: authentication/rtcstats-authentication.yml
  - type: Conventions
    url: conventions/rtcstats-conventions.yml
  - type: ErrorCatalog
    url: errors/rtcstats-problem-types.yml
  - type: DataModel
    url: data-model/rtcstats-data-model.yml
  - type: RateLimits
    url: rate-limits/rtcstats-rate-limits.yml
  - type: JSONSchema
    url: json-schema/rtcstats-analyze-response-data-schema.json
  - type: JSONSchema
    url: json-schema/rtcstats-observation-types-response-schema.json
  - type: JSONSchema
    url: json-schema/rtcstats-enrich-response-schema.json
  - type: JSONSchema
    url: json-schema/rtcstats-quota-response-schema.json
  - type: JSONSchema
    url: json-schema/rtcstats-sessions-list-response-schema.json
- aid: rtcstats:rtcstats-mcp-server
  name: rtcStats MCP Server
  description: Hosted Model Context Protocol server over Streamable HTTP, so coding agents can query analyzed WebRTC sessions.
    Tools get_quota, list_sessions, get_session and get_observation_explanation. Bearer JWT auth with the same application
    token as the REST API (an unauthenticated initialize returns 401 with WWW-Authenticate Bearer). Available on the Developer
    plan and above.
  humanURL: https://rtcstats.com/integrations/mcp
  baseURL: https://api.rtcstats.com/v1.0/mcp
  tags:
  - MCP
  - WebRTC
  - Observability
  properties:
  - type: MCPServer
    url: mcp/rtcstats-mcp.yml
  - type: Documentation
    url: https://rtcstats.com/integrations/mcp
  - type: AgentCard
    url: https://rtcstats.com/.well-known/agent-card.json
  - type: Authentication
    url: https://rtcstats.com/api-docs#authentication
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 92
  at: '2026-08-09T14:08:11.996Z'
x-correction-request:
  requested: '2026-09-28'
  source:
  - https://github.com/api-evangelist/rtcstats/pull/3
  request: 'Provider PR #3 (tsahilevi, 2026-09-26): its well-known re-probe is committed as well-known/rtcstats-well-known.yml
    (all 16 rows re-verified 2026-09-28; agent card now has 4 skills). Add pointers: security.txt, api-catalog and agent-card.json
    on both rtcstats.com and api.rtcstats.com. The provider also asked that the profile point at their own https://rtcstats.com/apis.yml
    (200 application/yaml): hand-merge its facts, record it as the provider-hosted index, never apply it. MCP answers 401
    with bearer auth as expected.'
  applied: '2026-10-03'
  applied_note: 'Applied by hand 2026-10-03, every URL re-checked live (200 with the expected content type; a nonexistent
    /.well-known path returns a real 404 on both hosts). Added APICatalog, AgentCard and SecurityTxt pointers for rtcstats.com
    and api.rtcstats.com (identical documents on both hosts; agent card protocolVersion 0.3.0, four skills), a WellKnown pointer
    to the probe file, and https://rtcstats.com/apis.yml as the provider-hosted APIsJSON index. Hand-merged from that index
    the pointers the profile lacked (deprecation, changelog, compliance/subprocessors, finops.json, rate limits, the schemas/
    Postman, Spectral, vocabulary, JSON Schema, JSON-LD, conformance and overlay files, the open-source collector docs, the
    provider-hosted OpenAPI) and the rtcStats MCP Server as an API entry (initialize answers 401, WWW-Authenticate Bearer).
    Not merged: the index calls the collector Apache-licensed, but GitHub reports rtcstats/rtcstats, rtcstats-server and rtcstats-js
    as MIT, so the MIT record stands.'
  earlier:
    requested: '2026-09-27'
    source: https://github.com/api-evangelist/rtcstats/issues/2
    request: 'Well-known probe is stale (generated 2026-08-09): since v1.10 security.txt and other /.well-known paths return
      200 on rtcstats.com and api.rtcstats.com. Re-run the well-known harvest on both hosts. Also asks how provider-published
      artifacts should be submitted -- answer on the issue.'
x-enrichment:
  date: '2026-10-31'
  status: nochange
  artifacts_added: 0
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

rtcStats API — frequently asked questions

Does rtcStats have an API?

Yes. APIs.io lists 2 APIs from rtcStats, including rtcStats API and rtcStats MCP Server.

Is there an OpenAPI specification for the rtcStats API?

Yes. APIs.io indexes 1 OpenAPI specification for rtcStats, each linked for download from this page.

How do I authenticate with the rtcStats API?

rtcStats uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Rtcstats Authentication.

How much does the rtcStats API cost?

rtcStats publishes its prices; its Free plan is $0/month as of 2026-10-28. APIs.io lists 6 pricing plans for rtcStats, with each plan's price, limits and inclusions under Pricing on this page.

Does rtcStats have an MCP server?

Yes. APIs.io lists 1 MCP server for rtcStats: rtcStats operates a first-party hosted MCP server over Streamable HTTP at https://api.rtcstats.com/v1.0/mcp. It is stateless JSON-RPC 2.0 and is also declared in the OpenAPI as the mcpStreamablePost o

Is the rtcStats API ready for AI agents?

rtcStats has a Kin Score of 66.8 out of 100 (exemplar) and an Agent Readiness score of 48.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/rtcstats"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/rtcstats/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/rtcstats/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.