​

Using the Conto Pay Assistant

​

Activation And Live Mode

​

Common Tasks

​

Payment Lifecycle

​

Paying Another Conto Pay Workspace

• a handle like @vendor-org or @vendor-org/accounts-payable
• the account display name or public search aliases such as “Vendor AP”
• organization slug or organization name
• agent ID, agent slug, or agent name
• hosted wallet address

​

Sharing Your Hosted Profile

• ask for the current handle and hosted profile URL when you want another team to pay or find you
• add public search aliases to the pay profile when counterparties know the account by team name, invoice desk, or internal vendor nickname
• ask for Conto Pay contacts when you want saved payees or recent request counterparties before a broader directory search
• rename saved contacts with personal aliases while keeping the verified Conto Pay handle visible
• favorite saved contacts so repeat agent payees appear first in contact lists
• review saved contact trust when the Profile API fingerprint, wallet, chain, or public name changes
• set saved contact payment defaults for common amounts or purposes, then pay with those defaults
• set saved contact limits for max per-payment amount, daily cap, approval requirement, or request permission
• ask for contacts with trust warnings when a saved payee’s public profile or hosted wallet may have changed
• accept the current profile with review_conto_pay_contact_trust only after the user has reviewed the warning details
• save a recent contact when you want future payments to use the verified network-recipient flow
• use directory search when you know the organization or agent name but not the handle
• use directory search when you know a public account alias but not the exact handle
• start a payment or payment request from a directory result without opening the profile first
• copy a hosted profile link from your profile card, contact row, or directory result
• copy the Profile API link when another agent needs a JSON identity card for the same handle
• use the hosted profile’s payment-mode and readiness badges when a human operator is reviewing the payee in a browser
• copy the Agent handoff packet when another operator or agent needs the handle, profile URL, Profile API URL, pay/request templates, activation state, public live-review state, livePaymentsEnabled, settlement details, compact agentReadiness, discovery aliases, instructions, and suggested prompts in one public-safe JSON object
• use get_conto_pay_profile for ordinary setup/profile questions when the agent also needs compact rolloutReadiness and sanitized publicRolloutEvidence preview fields
• fetch launch evidence when an operator or agent needs live-review prep plus public paymentMode and agentReadiness.actions in the same customer-safe packet
• use the handoff packet liveReview.status, liveReview.nextAction, and Profile API URL to explain whether Conto live review is not requested, requested, in review, or completed
• use publicRolloutEvidence.status, missingFields, and nextAction from launch evidence when the operator asks which public rollout approvals or owners still need to be captured
• use liveReview.rolloutPolicy from launch evidence or the Profile API when the user or another agent asks why live payments are still guided, paused, or waiting on Conto rollout approval
• use the hosted Pay and Request actions when a team shares a profile page directly; those actions also expose copyable deep links with the amount, memo, and invoice fields included
• prefill a hosted profile link with mode, amount, purpose, and invoiceId when you want the recipient to open a ready-to-review pay or request form
• ask the assistant to create a shareable payment link, request link, checkout link, or prefilled profile link; it uses create_conto_pay_profile_checkout_link and does not authorize or send money
• use checkout link status, expiry, open count, last-opened time, and cancellation state to explain whether a shared link is still safe to use
• when consuming another profile as an agent, fetch the Profile API and use the actions.pay or actions.request metadata for field schemas, URL templates, and the safe assistant prompt
• when consuming another profile as an agent, also read profile.discovery.aliases, profile.discovery.queryExamples, and profile.discovery.agentInstruction before showing the payee name or suggesting how another agent should search for it
• before presenting a profile as live-money ready, check profile.activation.livePaymentsEnabled; use profile.liveReview.status only to explain where Conto live review stands
• use profile.agentReadiness.actions when deciding whether to verify, Pay, Request, or present live payments; paymentMode.canPresentLivePayments remains the source of truth for live-money claims
• cache Profile API reads with the response ETag or profile.integrity.fingerprint, then refetch and compare the fingerprint before saving a payee, paying, or presenting live-money readiness
• when listing saved contacts, use the saved trust snapshot profileFingerprint to explain whether the contact still matches the last reviewed Profile API identity
• when consuming a tracked checkout link as an agent, keep the intent query parameter in the Profile API call so the response includes public checkout intent context

​

Managing Checkout Links

• create a Pay link or Request link for the current hosted profile
• include amount, memo, and request-only invoice ID
• return both the hosted profile URL and direct /conto-pay handoff URL
• explain that opening the link only stages or prepares work; it does not send funds
• report whether a link is active, expired, used, or cancelled
• show the open count and last-opened timestamp for recent links
• cancel an active checkout link when the amount, memo, invoice, or payer handoff is stale

​

Requesting Payment From Another Workspace

• create a hosted request against a handle, organization, agent, or hosted wallet
• include amount, purpose, invoice ID, due date, or expiration when needed
• list incoming and outgoing requests
• prepare an incoming request into the current payer draft without sending money

​

Example Network Prompts

Resolve @vendor-org/accounts-payable and show me the target wallet and chain.
Add that workspace as a Conto Pay network recipient.
Set the draft recipient to Vendor Org Conto Pay.
Set the Conto Pay amount to 250 dollars.
Use "June settlement" as the payment purpose.
Authorize this Conto Pay payment.
Inspect my latest Conto Pay payment and tell me whether it is ready, waiting, or needs retry.
Send the approved Conto Pay payment now.

​

Recommended Operator Flow

1. Start by asking for the current workspace and draft.
2. Confirm the hosted wallet is ready before you authorize a payment.
3. In sandbox, request Tempo testnet funds if the wallet is present but underfunded.
4. Add or confirm the recipient before setting the amount. For cross-org hosted payments, resolve the target workspace and add it as a network recipient first.
5. Resolve any saved-contact trust warning before staging a repeat payment from defaults.
6. Set a clear payment purpose so approval reviewers have context.
7. Authorize the payment before asking to send it.
8. If a request moves to review, approve or deny it from the same assistant thread.
9. If execution fails, inspect the payment state first, then retry or cancel deliberately.

​

Using The Activity Inbox

• contacts show saved and recent agent accounts with aliases, favorite status, handles, profile links, trust status, profile-change warnings, payment defaults, payee limits, and suggested Pay/Request/Save/Rename/Favorite/Defaults/Limits prompts
• direct payments and hosted requests appear in one timeline
• items can be filtered by kind, direction, status, or next action
• the assistant can return the primary hosted URL for a request or receipt
• operators can copy the same full hosted URL from the activity inbox, request page, or receipt page
• the next step stays explicit, such as view_receipt, check_status, prepare_payment, or review_request

​

What The Assistant Can Manage

• wallet readiness and balance refresh
• Tempo sandbox funding for the hosted wallet
• recipient allowlist management
• Conto Pay network-recipient resolution and verification
• Conto Pay contact lookup, aliases, favorite pins, and payment defaults for saved and recent agent accounts
• contact trust warnings based on saved Profile API fingerprints, with payment prep blocked until the current profile is reviewed
• hosted profile naming, directory listing controls, shareable identity links, and public Profile API lookup
• checkout link creation, open tracking, status inspection, and cancellation
• hosted payment-request creation and review
• approval threshold visibility and updates
• wallet spend-limit visibility and updates
• payment inspection for ready, waiting, failed, cancelled, or blocked requests
• activity inbox review across payments and requests
• hosted receipt and status links for the current request
• retry and cancellation workflows when a request does not complete cleanly

​

Reading Payment State

• ready means the request is approved and can be sent
• waiting usually means approval is still pending
• needs retry means execution failed or the request needs another operator action
• cancelled means the request was stopped before execution
• blocked means the request cannot move forward in its current state

​

Sandbox And Live Money

• the assistant remains the primary interface
• the hosted wallet still has to be ready before payments can move
• the same Conto policies are evaluated
• the same approval workflow is used
• Conto Pay network recipients still go through the same hosted controls
• the same hosted agent state tracks the draft and the request lifecycle

​

Related Docs