Using the Conto Pay Assistant
Conto Pay is meant to feel like an agent, not just a wallet screen. The assistant is the main way to operate the hosted workspace: it keeps track of the current payment draft, manages recipients, routes approvals, and executes approved payments.Common Tasks
| Goal | Example prompt |
|---|---|
| Check workspace status | Show me my Conto Pay workspace and payment draft. |
| Add a recipient | Add Acme Labs as a Conto Pay recipient at 0x1234... |
| Set the payment target | Set the draft recipient to Acme Labs. |
| Set the amount | Set the Conto Pay amount to 250 dollars. |
| Add a purpose | Use "April data labeling invoice" as the payment purpose. |
| Authorize the request | Authorize this Conto Pay payment. |
| Review approvals | List pending Conto Pay approvals. |
| Approve a payment | Approve the latest Conto Pay payment. |
| Deny a payment | Deny that payment and explain why. |
| Send after approval | Send the approved Conto Pay payment now. |
Payment Lifecycle
Recommended Operator Flow
- Start by asking for the current workspace and draft.
- Add or confirm the recipient before setting the amount.
- Set a clear payment purpose so approval reviewers have context.
- Authorize the payment before asking to send it.
- If a request moves to review, approve or deny it from the same assistant thread.
Sandbox And Live Money
The default Conto Pay workspace is sandbox-first, but the operating model stays the same:- the assistant remains the primary interface
- the same Conto policies are evaluated
- the same approval workflow is used
- the same hosted agent state tracks the draft and the request lifecycle
Related Docs
Conto Pay Overview
Learn what Conto Pay provisions and how it differs from self setup
Approval Workflows
Understand the review path for requests that need a decision