Dashboard assistant

The dashboard assistant (Conto AI in the panel header) answers questions about your Conto account and prepares dashboard changes for you to confirm. It works in your active organization with your dashboard role.

​

What it can help with

Use it to:

• find agents, wallets, balances, policies, payment requests, transactions, alerts, approvals, counterparties, and Conto Pay contacts
• summarize balances, recent activity, and policy results
• prepare changes for you to review and confirm, such as agent and wallet settings, spending policies and policy templates, bulk pauses or limit changes across agents, approval workflows, counterparties and recipient controls, approval decisions, and Conto Pay payments
• explain errors and suggest a safe next step
• check your plan, which agents have a test card, and what an agent still needs before its integration can make a card purchase

Read requests do not change account state. For time-sensitive information such as balances and payment status, ask the assistant to refresh the result before acting on it. Available actions depend on your role, organization, and the part of the product you are using. The assistant cannot create agents, create wallets, or generate SDK keys. Use the dashboard for those. It also cannot make or simulate a card purchase, and no dashboard page does. Your agent’s integration makes purchases with the agent’s SDK key. See test cards in the SDK guide.

​

How to use it

1. Sign in to Conto and select the intended organization.
2. Click the sparkle button at the bottom right of any dashboard page, or press Ctrl/⌘J.
3. Ask for one clear outcome and include the relevant agent, wallet, payment, or policy name.
4. Review the confirmation card and confirm only when the details are correct.

Example prompts:

• “Show my agents and their status.”
• “Summarize this week’s payment activity.”
• “Which approvals need attention?”
• “Explain why the last payment from the Research agent was denied.”
• “Set a $100 daily spend limit for the Research agent.”

Avoid combining unrelated changes in one request. Smaller requests are easier to verify and safer to retry.

​

Permissions and confirmation

The assistant does not bypass Conto permissions or spending controls. Each action requires the same role as the matching dashboard page, and the role is checked again when you confirm. Some changes require owner or administrator access. Payment policies can still deny a request or require a separate approval. The assistant cannot reveal credentials or bypass authentication. Every change, except Conto Pay draft edits and contact renames or favorites, appears as a confirmation card and applies only after you confirm it. The card shows a one-line summary and key details, such as the current and new limit, the policy scope, or the recipient’s full wallet address. If the underlying details change before you confirm, the change is not applied and the assistant offers to prepare it again. The assistant prepares one change at a time and reports the actual result after it runs. Before confirming an action, check:

• the organization and environment
• the affected agent, wallet, policy, or payment
• the recipient, amount, asset, network, and purpose for any financial action

​

Financial actions

Payment-related actions use the same policy checks, approval requirements, and execution safeguards as the corresponding dashboard or API flow. These confirmations can move funds:

• Final approval on a managed-wallet payment. Conto re-checks your policies, then sends the payment. The confirmation card says so. An approval that is not the last required one only records your decision.
• Final approval on an external-wallet payment. The payment is approved, but Conto does not send it. The agent sends the transfer and confirms it.
• Conto Pay send. Conto Pay checks the payment against wallet policies and sends it when they pass. It can also end up waiting for approval.

If the result is uncertain because of a timeout or connection problem, ask for the current payment status before attempting the action again. Starting a second payment can create a duplicate.

​

Conto Pay

The assistant finds Conto Pay profiles and saved payees, prepares payments and payment requests, creates Pay and Request links, and reports a payment’s status and next action. Preparing a payment or request does not send funds. Give the amount, currency, and purpose, plus an exact handle, payee name, invoice reference, or payment reference when you have one. This reduces ambiguity and makes the result easier to verify. Before you confirm a Conto Pay payment:

• Ask which organization, payment mode (Test payments or Live payments), wallet, network, and available balance are in use. Use test funds for setup and workflow testing.
• Confirm the payee’s display name, exact handle, wallet destination, and network. Use an alias only after confirming which profile it represents.
• If a saved profile has changed, review the current profile before continuing.
• A handle that is not a saved payee yet must be saved as a contact before the payment can be authorized.
• Ask for the policy result and next action. Ask to send only after the payment is ready.

Preparing a payment request loads its details for the payer to review. It does not make the requester an approved payee. Before authorizing payment, check the handle and wallet address, then select Save as trusted contact in the Conto Pay dashboard. The assistant can create a Pay or Request link with an amount, note, or invoice reference. It cannot set a link’s expiry or cancel a link. Links expire after 30 days. To cancel one, open Manage Conto Pay > Links. For an approval, use its dashboard link to review the amount, recipient, purpose, and decision history before acting. For reconciliation, ask for recent completed payments, their receipts, and the associated request or invoice references. Use Manage Conto Pay > Insights for a broader activity summary or a CSV export, and Manage Conto Pay for large comparisons or detailed configuration. See Conto Pay for profiles, links, requests, and moving to live payments.

​

Context and memory

The assistant knows which dashboard page you have open, so on an agent’s page you can ask about “this agent” directly. It keeps each conversation, including what it looked up, for 7 days so follow-up questions have context. Clear starts a new conversation.

​

Handling sensitive information

Do not paste private keys, seed phrases, passwords, API keys, or authentication cookies into the assistant. Refer to resources by their Conto name.

​

If a request cannot be completed

The assistant may ask for a missing detail, explain that your role lacks access, or direct you to a dashboard page.

​

When to use another surface

• Use the dashboard directly when you want to compare many records or edit a detailed form.
• Use the TypeScript SDK for application integrations.
• Use the MCP server to connect an MCP-compatible agent with an agent SDK key.
• Use Conto Pay for the hosted payment workspace.