> ## Documentation Index
> Fetch the complete documentation index at: https://please.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Product status

> What is available today, what is still a preview, and how to interpret the control-plane interface.

Please is being released in deliberate stages. This page separates the current service from the intended production experience.

## Available today

| Capability          | Status    | What it means                                                                                                           |
| ------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------- |
| Marketing website   | Available | Public information about the product and its safety principles.                                                         |
| Interactive web app | Demo      | A frontend demonstration using illustrative agents, policies, budgets, funding context, activity, plans, and responses. |
| Public MCP service  | Preview   | Stateless discovery and one-shot, read-only simulation for supported structured actions.                                |
| Support             | Available | Product and security questions by email at [hello@please.xyz](mailto:hello@please.xyz).                                 |

## Not available in the public product today

* Operator, tenant, or agent accounts
* Durable policies, budgets, approvals, or audit history
* Connected or embedded wallets
* Live portfolio aggregation
* Transaction approval, signing, submission, or broadcasting
* Policy-authorized, autonomous, or recurring financial actions
* Custody of user funds

<Warning>
  A demo approval screen does not approve a blockchain transaction. A simulation result does not mean that an action executed, confirmed, or will succeed later.
</Warning>

## Intended control-plane experience

The intended product will give operators one place to manage agent identity, funding sources, policies, budgets, approvals, activity, receipts, exceptions, and emergency controls. Portfolio data remains supporting funding and exposure context.

Before any production payment, wallet, or transaction feature is released, please will publish updated documentation covering authentication, custody, signing, data handling, supported networks, fees, recovery, reconciliation, and incident controls.

Every transaction-capable release must preserve a clear boundary:

1. The agent requests an outcome.
2. Deterministic policy allows, asks, or denies the exact request.
3. A permitted request reserves the applicable budget and authority.
4. The planning engine creates and simulates a bounded plan.
5. Material or exceptional actions receive independent approval.
6. The control plane revalidates, submits through a protected signer, and records settlement, delivery, finality, or reconciliation separately.

## How to read these docs

Pages that describe the current public service use terms such as **preview**, **simulate**, and **read-only**. Pages that describe the intended authenticated control plane are labeled **planned** or **intended**.

If the interface and documentation ever disagree, stop and contact [support](https://please.xyz/support) before taking action.