---
title: "Availability and boundaries"
description: "What the Agentic purchase preview implements today and what remains unavailable."
image: "https://help.agent.mq/og.svg"
---

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

# Availability and boundaries

## Implemented in the preview source

- Application-owned purchase intents and redacted state.
- Revision-checked checkout digest approval and pre-commit cancellation.
- Exclusive, origin-bound browser handoff leases.
- Persistent redacted events, one-attempt enforcement, budgets, wallet references, secure-input session records, refund records, and reconciliation records.

## Not a production capability

- Arbitrary-site browser execution and cart completion.
- Production Link wallet integration.
- Production PayPal wallet integration for third-party merchants.
- Unattended payment completion.
- Storage or retrieval of passwords, OTPs, card numbers, CVVs, cookies, or wallet tokens.
- A public endpoint that hands payment material to an Agent.

## Why the boundary is explicit

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.

## See also

- [Purchase state model](/agentic-purchases/state-model)
- [Private and callback endpoints](/reference/private-endpoints)

Source: https://help.agent.mq/agentic-purchases/availability/index.mdx