You connect an assistant the way you sign in to an app with your Payve account: the assistant sends you to Payve, you approve, and it is connected. No API key is created, so there is no key to store or leak.
Connecting by sign-in is in early access. If your assistant reports that the address below does not answer, ask support to enable it for your account.

Connect

1

Add Payve to your assistant

In your assistant’s settings, add a new MCP server (some assistants call it a connector) with this address:Start with Sandbox.
2

Sign in to Payve

The assistant opens Payve in your browser. Sign in to the dashboard if you are not already.
3

Check what is being asked

The page shows the app that is asking, the business and environment it will reach, and what it wants to do: read your account, and optionally resend webhooks.
4

Approve

Select Approve. You return to the assistant, connected. Select Deny to stop; nothing is shared.
5

Ask a question

Ask “What are my Payve wallet balances?”. It should list your wallets.
You need a verified email address and a dashboard role that can manage developer settings. The business owner gets an email each time an assistant is connected.

Which assistants can connect

Unverified app means Payve has not checked who runs the app. Approve one only if you started the connection yourself, just now. If a link to an approval page reached you by email or chat, do not approve it.

See and remove connections

Go to Settings → Connected assistants. Each connection shows the app, the environment, what it may do, when it was connected and when it was last used. Select Disconnect to end one. It stops working at once. A connection also ends when:
  • you reset your password or sign out of all sessions,
  • the person who approved it leaves the business or loses the role that allowed it,
  • 90 days have passed since it was approved. Connect again to continue.

Good practice

  • Connect in Sandbox first. Confirm the assistant behaves as you expect before you connect a live account.
  • Read what is being asked. The approval page lists exactly what the assistant will be able to do. Deny it if that is more than you want.
  • Check before you act. An assistant can misread a list. Confirm a figure in the dashboard before you act on it.
  • Mind what you share. Whatever the assistant reads becomes part of your conversation with it, including recipient names and account numbers.

Run it yourself with an API key

If your assistant cannot connect by sign-in, you can run the MCP server on your own machine with an API key. Ask support for the package.
Create a separate key for the assistant so you can revoke it on its own. Read scopes cover every lookup; add payouts:write or conversions:write only if you want it to resend those webhooks. Leave PAYVE_API_URL out to use the live API.