---
title: "Browser handoff leases"
description: "Give one authenticated person temporary control on the exact merchant origin."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser handoff leases

<p>A handoff is an exclusive lease on human control, not a credential handoff. One row per purchase records the holder, allowed merchant origin, expiry, and revision.</p>
<p>Claim the lease</p><p><code>POST /v1/applications/{appId}/purchases/{purchaseId}/handoffs</code> accepts an empty JSON object. A claim is refused while another holder’s lease is live.</p><p>Read the allowed origin and expiry</p><p><code>GET /v1/applications/{appId}/purchases/{purchaseId}/handoffs/{handoffId}</code> returns the redacted lease.</p><p>Release it</p><p>The holder calls <code>/complete</code> after finishing the human step, or <code>/cancel</code> to return control without completing it. Both writes echo <code>expectedRevision</code>.</p>
<h2 id="verify">Verify</h2>
<p>A non-holder cannot release the lease. Claims are blocked after the payment commit boundary, and an active lease is revoked when the purchase is cancelled or begins its single payment attempt.</p>
<h2 id="next-steps">Next steps</h2>
<ul>
<li><a href="/agentic-purchases/state-model">Purchase state model</a></li>
<li><a href="/help/security">Security and contact</a></li>
</ul>

Source: https://help.tooluse.net/agentic-purchases/handoffs/index.mdx