agenticweb.wiki

Web Agent Protocol (WAP) WAP

By Belgravia Labs Standards Observatory · Last verified · 4 primary sources

Web Agent Protocol (WAP) is an agentic-web standard (document format) at step 5, Act, governed by Single company; its status is "Dormant: last commit 2025-06-03". It answers: "How does a recorded human browsing session get replayed reliably by an agent later, or turned into a reusable tool another agent can call?" Replacing or extending macro record-and-replay, packaged as an MCP tool, implementation status is prototype, last verified 2026-10-23.

Act Web Agent Protocol (WAP), published by OTA Tech AI, is a record-and-replay framework for browser automation: a Chrome extension captures a human's on-page interactions (clicks, form fills, navigation) into a structured event stream; a Python SDK converts that stream into either an 'exact-replay' list (reproduces every recorded action verbatim) or a 'smart-replay' list (condensed, goal-oriented steps generated via an LLM subgoal-generation step); and a separate WAP-Replay component executes either list back against a live browser, with an option to package a recorded task as a local MCP server so any MCP-speaking agent can reuse it as a tool [1].

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 September 2026,, the project shows no recent development activity: its most recent commit is dated 2025-06-03, over a year, 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.

Instances

Verified SDKs, reference implementations & validators:

See also

Comparisons

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. The live site stopped answering in October 2026; this is the archived copy from 2026-06-07. — http://web.archive.org/web/20260607080002/https://www.otatech.ai/ (2026-09-06) VERIFIED
  3. Web Agent Protocol is dormant: last commit 2025-06-03 — https://github.com/OTA-Tech-AI/web-agent-protocol (2025-06-03) VERIFIED
  4. No push since 2025-06-19 (over 180 days) — https://github.com/OTA-Tech-AI/web-agent-protocol/releases/tag/wap-replay-tool-1.0.0 (2025-06-01) REPORTED

Verification log and errata

JSON · Markdown · OKF v0.2

Frequently asked questions

What is Web Agent Protocol (WAP)?
Web Agent Protocol (WAP) is an agentic-web standard (document format) at step 5, Act, governed by Single company; its status is "Dormant: last commit 2025-06-03". It answers: "How does a recorded human browsing session get replayed reliably by an agent later, or turned into a reusable tool another agent can call?" Replacing or extending macro record-and-replay, packaged as an MCP tool, implementation status is prototype, last verified 2026-10-23.
What is the adoption and standardization status of Web Agent Protocol (WAP)?
Dormant: last commit 2025-06-03, governed by Single company (OTA Tech AI); MIT-licensed public GitHub repository; no independent standards process or multi-party governance found. Implementation: prototype. Version: unversioned (main branch, 1 tag, last commit 2025-06-03) (2025-06-03). Last verified 2026-10-23.
How does Web Agent Protocol (WAP) compare to other act protocols?
Web Agent Protocol (WAP) is one of 13 standards at step 5, Act (Do something for me). It pairs with Model Context Protocol, WebMCP. Head-to-head comparisons on this site: DOM Browser Automation vs WebMCP & MCP, WebMCP. Every standard at this step is listed at https://agenticweb.wiki/category/act/.