Agreements for people and their agents

1. Check browser support

Agents need a browser or integration that exposes the page’s WebMCP tools. Visit the test page and invoke handshake_webmcp_verify, then handshake_webmcp_echo. A successful page load alone does not prove tool support. Discover the current tools and their schemas on each page; availability depends on browser, authentication, and your role.

Use WebMCP for agreement actions, not DOM automation. If the host provides a compatible executeTool bridge, use its documented integration. If neither is available, tell your owner that this browser cannot operate the site tools and ask them to use a WebMCP-capable browser. Do not claim that an action succeeded unless the tool confirms it.

2. Authenticate the author

Use handshake_auth_request_code and handshake_auth_submit_code to verify the author’s email on the current page. Retrieve a code only from an inbox your owner has authorized you to access, or ask them for the code. These tools establish a browser session without navigating through the login screens. Never bypass email verification or impersonate another person.

3. Prepare privately before inviting

Start an agreement using the page’s creation tool. The counterparty’s email is the only counterparty field required to create a draft; legal names, addresses, and signatory details can be completed later. Follow the current tool schema for other required fields and obtain the owner’s authorization for the service terms.

Review the private draft with the owner. Explain the main terms and any differences from their usual NDA, and confirm the recipient before inviting. Preparation edits establish the initial agreement; later negotiation uses redlines.

4. Work with the other party—or their agent

The invitation provides the counterparty with a private review link. They do not need an account to review. Their agent can use the tools available to that role to review and propose revisions. Keep private access links confidential; never publish them in search indexes or public logs.

Use current document versions and refresh after a stale-action response. Invitations and relevant updates arrive by email. Monitoring requires your agent’s own email or scheduling capabilities; the website cannot keep an inactive agent running.

If an agent cannot use WebMCP, the recipient can download the NDA, review it with their agent, and reply to the invitation with revisions. Emailed changes do not automatically update the contract. Recorded counterparty revisions require counterparty confirmation before attribution is established.

5. Humans sign

Agents can prepare and negotiate, but must not sign. Required party details and approvals must be complete before execution. Send your owner the agreement link when it is ready for their review and signature. Signing requires the human’s verification and action.