zapo.to valid
Zapo
The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://zapo.to/llms.txt
- llms-full.txt
- https://zapo.to/llms-full.txt
- Sections
- 9
- Links
- 52
- Size
- 11278 bytes
- 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-26T00:39:16.307Z
- Last checked
- 2026-10-26T00:39:18.534Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T00:39:16.319Z. Cached copy · Source on zapo.to
# Zapo
## Getting started
- [Introduction](https://zapo.to/en/introduction.md): zapo is a high-performance TypeScript implementation of the WhatsApp Web protocol, built for high-scale, multi-session bot and automation workloads.
- [Installation](https://zapo.to/en/installation.md): Install zapo-js with npm, pnpm, or yarn, choose a storage backend for credentials, and add the optional peer dependencies your features depend on.
- [Quickstart](https://zapo.to/en/quickstart.md): Connect a WhatsApp session, scan the QR code or use a pairing code, and reply to your first incoming message in under five minutes with zapo.
- [Migrating from Baileys](https://zapo.to/en/guides/migrating-from-baileys.md): Coming from Baileys? Here's how the connection lifecycle, store layout, message API, and event names map onto zapo's coordinator-based client.
- [Use the docs from your AI assistant](https://zapo.to/en/use-with-ai.md): Pull these docs into Claude Code, Cursor, ChatGPT, or any MCP-capable agent — three integration paths, no setup on our side.
## Core concepts
- [Architecture](https://zapo.to/en/concepts/architecture.md): How the WaClient, coordinators, stores, transport, and event flow fit together inside zapo, and how data moves from WhatsApp into your code.
- [Authentication](https://zapo.to/en/concepts/authentication.md): Pair a device with a QR code or 8-character pairing code, persist Noise credentials across restarts, and cleanly log out of a WhatsApp session.
- [Identities: phone numbers & LID](https://zapo.to/en/concepts/identities.md): How WhatsApp's phone-number JIDs (PN) and privacy LIDs differ, why both exist in multi-device, and how zapo maps and resolves between them.
- [Configuration](https://zapo.to/en/concepts/configuration.md): Configure WaClient: sessions, timeouts, history sync, presence on connect, addons, proxy, logging, logout cleanup, and production knobs.
- [Plugins](https://zapo.to/en/concepts/plugins.md): Extend WaClient with typed plugins: register stanza handlers, expose new coordinators at client[exposeAs], and contribute typed events that only exist when the plugin is installed.
- [Events](https://zapo.to/en/concepts/events.md): Reference for every WaClient event you can subscribe to: messages, receipts, groups, history sync, app-state mutations, and failures.
- [Stores](https://zapo.to/en/concepts/stores.md): Persist authentication state, Signal sessions, and per-domain protocol data through zapo's pluggable store interface and bundled backend packages.
## Guides
### Messaging
- [Sending messages](https://zapo.to/en/guides/sending-messages.md): Send WhatsApp text, threaded replies, mentions, and rich link previews with client.message.send, the typed entry point for all outgoing content.
- [Raw proto sends](https://zapo.to/en/guides/raw-sends.md): Send content types WhatsApp supports but zapo doesn't have a typed builder for yet — locations, contact vCards, group invites, buttons, list menus, interactive native flow, pro
…Machine-readable: GET /v1/resolve?q=zapo.to · GET /v1/domain/zapo.to · 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 zapo.to, 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 zapo.to:
1. POST https://agentwebmap.com/v1/sites/zapo.to/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://zapo.to/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/zapo.to/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/zapo.to).
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.