rrweb.com valid
rrweb
rrweb records DOM changes and user interactions as structured events, then rebuilds those events for session replay. rrweb Cloud stores, indexes, queries, and serves rrweb recordings.
- Authority
- 46 reach 5 · trust 5 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://rrweb.com/llms.txt
- Sections
- 4
- Links
- 16
- Size
- 3223 bytes
- Popularity rank
- #999946
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T18:12:16.105Z
- Last checked
- 2026-10-26T11:58:33.009Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T11:58:30.957Z. Cached copy · Source on rrweb.com
# rrweb
> rrweb records DOM changes and user interactions as structured events, then rebuilds those events for session replay. rrweb Cloud stores, indexes, queries, and serves rrweb recordings.
**When to use rrweb:** reach for rrweb when a task needs an exact, inspectable record of what happened in a browser tab. It fits these jobs best: reproducing a bug report with the session that caused it, auditing what a browser automation or AI agent did on a page, watching a customer's session to support them, embedding session replay in your own product, and analysing how people use a page. rrweb records the DOM and user input as JSON events, so recordings stay small, searchable, and replayable at full fidelity.
**How to use it:**
- To record a page you operate, add `@rrweb/record` and store the events yourself, or add `@rrweb/browser-client` to send them to rrweb Cloud with a public write-only key.
- To replay events, use `@rrweb/replay` in your own UI or `rrweb-player` for a ready-made player.
- To find and fetch recordings in rrweb Cloud, call the API at `https://api.rrweb.com` from server code with a private key that has the required read scopes. The OpenAPI specification lists every operation.
Use rrweb Cloud when you want a managed backend for ingest, storage, indexing, querying, replay, and screenshots.
Review the privacy controls before recording production traffic. Mask sensitive input and block elements that should never enter a recording.
## Docs
- [rrweb documentation](https://rrweb.com/docs/): guides for the rrweb library, rrweb Cloud, and every package
- [rrweb docs for LLMs](https://rrweb.com/docs/llms.txt): the full documentation index in llms.txt format
- [rrweb open source guide](https://rrweb.com/docs/guide): record with @rrweb/record and replay with @rrweb/replay or rrweb-player
- [rrweb Cloud guide](https://rrweb.com/docs/cloud/): hosted ingest, storage, search, and replay
## API
- [rrweb Cloud OpenAPI specification](https://rrweb.com/openapi.json): machine-readable description of every rrweb Cloud API operation
- [rrweb Cloud API reference](https://rrweb.com/docs/cloud/api-reference): operations, parameters, and responses
- [rrweb Cloud authentication](https://rrweb.com/docs/cloud/authentication): API keys and session tokens
- [rrweb Cloud API keys](https://app.rrweb.com/api-keys): create and manage API keys in the dashboard
- [rrweb Cloud API base URL](https://api.rrweb.com): base URL for every API request
## Packages
- [@rrweb/record](https://rrweb.com/docs/packages/record/): capture DOM state, mutations, and user interactions
- [@rrweb/replay](https://rrweb.com/docs/packages/replay/): rebuild and replay an rrweb event stream
- [rrweb-player](https://rrweb.com/docs/packages/rrweb-player/): player UI for rrweb recordings
- [@rrweb/browser-client](https://rrweb.com/docs/packages/browser-client/): send browser recordings to rrweb Cloud
## Optional
- [rrweb on GitHub](https://github.com/rrweb-io/rrweb): the open source r
…Machine-readable: GET /v1/resolve?q=rrweb.com · GET /v1/domain/rrweb.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage rrweb.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for rrweb.com:
1. POST https://agentwebmap.com/v1/sites/rrweb.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://rrweb.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/rrweb.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/rrweb.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.