For agents and technical readers

Inspect account, payment and Mind readiness

Use the normal human account interface to distinguish organisation membership, billing state and a ready workspace without exposing an account-management API as an agent tool.

Contents

Preconditions and boundary

The human signs in to the intended organisation’s Mensara account. Billing actions require its owner. Account data is separate from customer records inside the Mind. Do not ask an agent for passwords, payment-card details or a copied browser session.

Inspect the normal account route

Open Overview and check organisation, Signed in as, Your role and Plan status.
Open Your Mind and inspect its address and actual handoff state.
If invited membership is incomplete, resolve that state through the supported account route before changing workspace access.
If a checkout already exists, inspect its original confirmation/status before starting another payment.

Payment received, plan active, provisioning pending and ready-to-open are different outcomes. A browser or payment response lost in transit is not permission to create a second charge.

Billing changes remain the human’s decision

When enabled for an owner with a billing account, Billing opens the hosted provider page. The human inspects amount, billing period, tax, terms and the effect of any change before confirming. A missing button may reflect role, enablement or no completed checkout. No universal price or cancellation policy is inferred from a source constant.

For transfer, cancellation or deletion, establish the intended scope/effective date, retained access and secure export/recovery custody first. Use the supported owner/account route and inspect its result. File export, billing cancellation and external credential revocation are separate operations.

Failure handoff

Keep the organisation, time, checkout/handoff reference and bounded error. Do not include card details, secret tokens, recovery material or private Mind records. Have the authorised account operator reconcile the original transaction/provisioning state before retrying.

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Inspect account, payment and Mind readiness

Operating procedures · For agents and technical readers · [How it works](https://app.mensara.ai/how-it-works)

Use the normal human account interface to distinguish organisation membership, billing state and a ready workspace without exposing an account-management API as an agent tool.

[Page as Markdown](https://app.mensara.ai/how-it-works/account-status-procedure.md)

[Human guide](https://app.mensara.ai/how-it-works/account-and-billing)

## Use the released interface with current authority

Availability: Core0.20.11 / Portal0.3.47 source checked; discover the actual installed client and enabled features.

Who can do this: The connected principal with the permissions named in this procedure

What changes: The procedure explains its actual reads, writes or external effects before action.

Limits: An input accepted by a source schema is not a successful installed-runtime task.; Keep human decisions, client exclusions and pending results explicit.

Verification: Source checked and independently reviewed; scoped runtime receipts are recorded separately.

## Preconditions and boundary

## Inspect the normal account route

1. Open **Overview** and check organisation, **Signed in as**, **Your role** and **Plan status**.
2. Open **Your Mind** and inspect its address and actual handoff state.
3. If invited membership is incomplete, resolve that state through the supported account route before changing workspace access.
4. If a checkout already exists, inspect its original confirmation/status before starting another payment.

Payment received, plan active, provisioning pending and ready-to-open are different outcomes. A browser or payment response lost in transit is not permission to create a second charge.

## Billing changes remain the human’s decision

When enabled for an owner with a billing account, **Billing** opens the hosted provider page. The human inspects amount, billing period, tax, terms and the effect of any change before confirming. A missing button may reflect role, enablement or no completed checkout. No universal price or cancellation policy is inferred from a source constant.

## Failure handoff

## Related

- [Manage your Mensara account and billing](https://app.mensara.ai/how-it-works/account-and-billing)
- [Back up, recover and export your Mind](https://app.mensara.ai/how-it-works/backup-restore-ownership)
- [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)

[Join the waitlist](https://app.mensara.ai/#waitlist)