---
title: "Availability and boundaries"
description: "What the Agentic purchase preview implements today and what remains unavailable."
---

> 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.

# Availability and boundaries

<h2 id="implemented-in-the-preview-source">Implemented in the preview source</h2>
<ul>
<li>Application-owned purchase intents and redacted state.</li>
<li>Revision-checked checkout digest approval and pre-commit cancellation.</li>
<li>Exclusive, origin-bound browser handoff leases.</li>
<li>Persistent redacted events, one-attempt enforcement, budgets, wallet references, secure-input session records, refund records, and reconciliation records.</li>
</ul>
<h2 id="not-a-production-capability">Not a production capability</h2>
<ul>
<li>Arbitrary-site browser execution and cart completion.</li>
<li>Production Link wallet integration.</li>
<li>Production PayPal wallet integration for third-party merchants.</li>
<li>Unattended payment completion.</li>
<li>Storage or retrieval of passwords, OTPs, card numbers, CVVs, cookies, or wallet tokens.</li>
<li>A public endpoint that hands payment material to an Agent.</li>
</ul>
<h2 id="why-the-boundary-is-explicit">Why the boundary is explicit</h2>
<p>The ledger can enforce state, approval, and audit rules before execution adapters are safe to expose. Documentation must not turn an implemented record type into a claim that money movement works end to end.</p>
<h2 id="see-also">See also</h2>
<ul>
<li><a href="/agentic-purchases/state-model">Purchase state model</a></li>
<li><a href="/reference/private-endpoints">Private and callback endpoints</a></li>
</ul>

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