Web Agent Protocol (WAP) WAP

Overview

It solves reliable browser-action reuse and agent-UI testing without requiring an agent to re-derive a working action sequence from scratch on every run — a common failure mode for pure browser-use agents that re-plan each step live. It does not define any network-visible, site-facing protocol: there is no well-known path, header, or endpoint a website exposes to signal WAP support, and no interoperability guarantee between WAP-recorded actions and any other agent framework's action format beyond the MCP-server conversion step. It is also not a standards-track specification in any formal sense — it is a single company's open-source tool with a README describing conventions, not a versioned spec document.

As of this check (September 2026), the project shows no recent development activity: its most recent commit is dated 2025-06-03, over a year before this verification pass, against 3 branches and a single tag ^[1]. Governance is entirely OTA Tech AI's own (a company also publishing the OTA-v1 model on Hugging Face); there is no independent standards body, working group, or multi-vendor input process. Adoption signals are limited to GitHub's own engagement metrics (507 stars, 88 forks, 61 watchers as observed during this pass) with no independent production deployment identified beyond the project's own demo materials. What is unresolved: whether WAP is still actively maintained at all given the year-plus commit gap, and whether its name collision with the unrelated, long-obsolete Wireless Application Protocol (also 'WAP,' a 1990s–2000s mobile-web standard) causes practical confusion — no evidence of such confusion was found, but the acronym overlap is exact.

Discovery and probe

None — WAP is not a network-discoverable, site-facing protocol. It is a local pipeline: a Chrome extension records a user's browser session, a Python SDK converts the recording into an 'exact-replay' or 'smart-replay' action list, and that action list can be converted into a local MCP server for reuse by any MCP-speaking agent.

n/a n/a — there is no remote origin to probe. WAP has no server-side or site-side presence to detect; every website it 'supports' is simply whatever page the operator's own Chrome extension happened to record, and replay runs entirely on the operator's own machine.
parse:     n/a
on absent: n/a — presence is determined by whether the operator has locally installed the OTA-WAP Chrome extension and Python SDK and generated a recording, not by any network-visible signal at a target site.

Not probed live: client-side. WAP records and replays browser actions; nothing is served by the site.

History

• 2026-09-06 — added from arXiv 2504.16736 survey comparison, verified against github.com/OTA-Tech-AI/web-agent-protocol
• 2026-09-06 — added second evidence entry (otatech.ai) to satisfy the two-source verification requirement

Instances

• OTA Technologies (Web Agent Protocol MCP server) · Observed 2026-03-18 · service

Every instance with its source is listed on the instances page.

See also

• Not to be confused with: Wireless Application Protocol (unrelated, legacy mobile-web WAP)

References

1. The OTA-Tech-AI/web-agent-protocol GitHub repository (MIT license, 507 stars, 88 forks) describes WAP as a record (Chrome extension) → convert (exact/smart replay lists) → replay pipeline for browser automation, including a path to convert recorded actions into an MCP server; its last commit ('Update README.md') is dated 2025-06-03, over a year before this check. — https://github.com/OTA-Tech-AI/web-agent-protocol (2026-09-06) VERIFIED
2. OTA Tech AI's own homepage (otatech.ai, 'OTA Technologies Inc.') lists Web-Agent-Protocol (WAP) alongside its OTA-v1 Browser Agent Model as company products, confirming WAP is a single-company project rather than an independently governed spec. — https://www.otatech.ai/ (2026-09-06) VERIFIED