Skip to content

Coding agents

If you write code with Claude Code, Codex or Cursor, you can drive this API from inside the editor: create orders, watch one confirm with no bank in the loop, and have the agent write a checkout and a webhook receiver that follow the rules on this site rather than the ones it learned from other payment APIs.

You need a test API key — it starts with vpt_ — from Settings → Developers. It works from the moment you sign up, before your account has seen a real payment. That is the whole setup.

/plugin marketplace add Cool-Solve/moneylanded-agent-toolkit
/plugin install moneylanded@moneylanded

You are prompted for the key when the plugin is enabled. It goes into your operating system’s keychain, never into a file in your project.

Terminal window
export MONEYLANDED_API_KEY=vpt_your_test_key
codex mcp add moneylanded \
--url https://api.moneylanded.com/mcp \
--bearer-token-env-var MONEYLANDED_API_KEY

Add this to .cursor/mcp.json, with MONEYLANDED_API_KEY set in your environment:

{
"mcpServers": {
"moneylanded": {
"url": "https://api.moneylanded.com/mcp",
"headers": { "Authorization": "Bearer ${env:MONEYLANDED_API_KEY}" }
}
}
}

Tools for the whole order lifecycle — create_intent, reserve_intent, get_intent, list_intents, cancel_intent, list_credits, attribute_credit — plus two that only exist for building:

  • simulate_credit synthesises a bank credit and pushes it through the same correlation path a real one takes. It is how an order confirms without money moving.
  • verify_webhook_signature checks a signature against a raw body, so a receiver can be proven correct before it ships.

Every page of these docs is also exposed as a resource, so the agent reads the real reference instead of recalling one.

A vpt_ test key can do anything. Its orders and credits are invisible to your live orders, reports and totals, and it has its own amount pool — a test order never takes an amount a real customer is about to be quoted. Order ids are per-mode too, so rehearsing order-1 does not burn it for your live books.

A vp_ live key is read-only through this endpoint. Reads work; every write is refused with a message naming the test key. An agent should not be able to create a real order against a real merchant by misreading a prompt, so it cannot. A live key on an account that is not switched on yet does not get that far: it answers 403 account_not_active.

create_intent → simulate_credit → get_intent reads confirmed → webhook fires

Pay the reserved paid_paise and it confirms. Pay an amount within ₹1 of a test order, but not its exact reserved amount, and it parks as unplaced with that order as its candidate and sends payment.unplaced — the most common real integration bug, on demand, before a customer ever finds it for you. A random amount is stored quietly and sends nothing; see Limits.

The toolkit ships guidance the agent loads automatically, because this API’s model is not the one other payment APIs taught it. Without it, an agent will reach for the familiar shape and write an integration that looks right and never confirms: passing an order id through the UPI note (it does not come back), matching a credit on the payer’s UPI ID (never a key), or rounding the amount for display (the amount is the order identity).

Those rules are all on this site. The skills are the same rules, in the place the agent will actually read them.

Cool-Solve/moneylanded-agent-toolkit — MIT. The skills are plain Markdown; read them before you install them.