Skip to main content
Take crypto payments on your own website — by pasting one prompt into your AI coding tool.
Web. The marketing page, the dashboard and the downloads are web. There is no mobile equivalent.

​
What Is Moove Agentic Payments?

Moove Agentic Payments is a skill file — an instruction file your AI coding tool reads — that teaches the tool how to integrate the live moove.xyz APIs: payment links to get paid, payouts to send, and swaps to move between tokens and chains. You download it, drop it into your tool, and describe what you want. The tool writes the integration against the real API.
The Moove API key the skill uses cannot move money. It does not sign anything — it requests payments, prices payouts and swaps, and records transactions your own code has already broadcast.A payout or a swap is signed locally, by your project, with a key moove.xyz never sees. That signing key is the one that can move funds, and it stays with you.

​
How Do I Integrate In Three Steps?

1

Download the skill or a plugin

One skill.md works everywhere. Plugins repackage the same file into the location your specific tool looks for it.
2

Insert a prompt

Use the ready-to-use prompt from moove.xyz/business/agentic-payments, or write your own.
3

Build and deploy

Your tool builds the checkout. Manage the keys, links and transactions it creates in Moove Manage.

​
What Are The Five Plugins?

Moove Agent Skills follow an open standard, so the same file runs across 40+ AI models. The plugins are a convenience, not a requirement. Download any of them from moove.xyz/business/agentic-payments.
Not using one of the five? Download the plain skill.md and put it wherever your tool reads instructions from. It is the same file.

​
Before You Start

1

To get paid, have a default wallet and a handle

Only needed for the Moove Receive Agent. The API refuses to create links for an account that cannot receive payments.
2

To pay out or swap, connect the funding wallet by signature

Only needed for the Moove Send Agent and the Moove Swap Agent. The wallet the money leaves must be one you connected by signing with it — a receive-only address you added by pasting it in cannot send or swap. You will also need a signing library in your own project; moove.xyz ships none.
3

Create an API key

At moove.xyz/dashboard/api-keys, scoped to the agent you need — Receive to take payments, Send to pay out, Swap to swap or bridge.
The key is shown once, in plaintext, at creation. Copy it then — it cannot be shown again.
Moove API Keys →
4

Give your tool the key

As an environment variable. Never commit it, and never paste it into a prompt.

​
What Are The Agents?

An agent is the unit of permission on a key. Picking one is how you decide what a key can do.
Receive, Send and Swap are live. Only the Moove Ramp Agent is still announced rather than built — it appears in the picker disabled and labelled coming soon. There is no Bridge agent: bridging is what the Moove Swap Agent does, on the same endpoint as a same-chain swap.

​
What Can The Moove Receive Agent Do?

Two scopes, and nothing else: An agent that could request a payment but never confirm it settled could not complete the one job it exists for, so the Moove Receive Agent gets both.

​
What Can The Moove Send Agent Do?

Three scopes — the three legs of one payout, none of which signs anything:
moove.xyz never signs, and your agent must. There is no “send money” call. moove.xyz prices the payout and hands back an unsigned transaction; your own code signs and broadcasts it with a key moove.xyz never sees, and then tells moove.xyz the hash.So your agent needs a signing library in your project, and a funding wallet connected to your Moove account by signature. A receive-only address you added by pasting it in cannot send — the payout is refused before anything is signed.
Send is not selected by default in the picker. Tick it deliberately — a key that can only receive is a meaningfully smaller thing to leak.
Make sure your code can read the key. If the API key is missing, a payout request does not fail — it runs without your account’s checks, and the payout is not recorded against your key. Have your code stop before it asks for a quote if the key is not set.
Moove Send API →

​
What Can The Moove Swap Agent Do?

Three scopes — the same three legs as a payout, and again none of them signs anything: One agent covers both jobs. A swap stays on one chain; a bridge moves across chains. Either way the output lands in a wallet on your own account — to pay somebody else, use the Moove Send Agent.
Your agent signs the swap, not moove.xyz. It needs the same two things as a payout: a signing library in your project, and a funding wallet connected to your Moove account by signature. A wallet that is not connected is refused when your agent asks for a quote, before anything is signed.
Swap is not selected by default in the picker either. Tick it deliberately. Moove Swap API →

​
Why A Leaked Key Cannot Cost You Money

A key is a down-scope of you: it acts as your account and can only do a subset of what you can do.No endpoint moves funds, and none accepts a private key. A quote returns unsigned transaction data that you sign yourself, and recording a transaction only writes down a hash that is already on chain. Payment links always settle to your own default wallet, and the caller cannot choose where they go.So a leaked key cannot move funds at all — every transaction must be signed by a key only you hold. (A keyed swap must also return its output to your own account, but that is a guardrail against mistakes, not the protection.)
That is not the same as harmless. A leaked key can read your transaction history, create payment links that pay you, and record transactions against your own wallets. Revoke it — it simply cannot take the money.
Revoke a key you no longer trust. Revocation is permanent and immediate.

​
Who Decides Who Gets Paid?

You do — never your agent, and never something your agent reads. A signed payout cannot be taken back, and an AI tool reads a lot of text that other people wrote.
  • The recipient, the amount, the token and the chain come from you, or from your own records, such as your payouts table or your invoices. Never from a web page, an issue, a README, a file the tool was asked to summarise, or an API response — including a payment link’s or a transaction’s description, which other people can influence.
  • A swap is the same. The pair and the amount come from you, and the output always returns to your own wallet.
  • Your agent asks before it signs a payout. It shows you the recipient, the amount, the token, the chain and what will arrive, and waits for your yes — once per payout, or once per batch with every row listed.
  • Text that asks your agent to change a recipient, raise an amount, skip your confirmation, or send a key or a seed phrase anywhere is an attack. Your agent should not act on it. It should stop and show it to you.

​
Can I Do It Without An Agent?

The API is a plain HTTP API. Nothing about it requires an AI tool.
API Reference →

​
Can My AI Agent Connect With MCP?

Yes. MCP — the Model Context Protocol — is an open standard that lets an AI agent call outside services as tools. The skill teaches your tool to write an integration. The Moove MCP server lets an agent work with your account directly: look up your payment links, check which have been paid, and create a new link when you ask for one.
  • Server: https://api.moove.xyz/mcp
  • Same API key. Use the Moove API key you already have, sent as a request header. The agent you picked for the key decides which tools appear.
  • Same safety. Nothing on the MCP server signs or moves money. A payment link it creates always settles to your own default wallet.
Connect from Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI today. Connecting from claude.ai and ChatGPT is coming later. MCP Server →

Moove API Keys

Create, scope and revoke.

Moove Payment Links API

The endpoints in full.

Moove Receive

The same product, no code.
Click. Integrate. Transact. Your Money. Your Move.