Payle for agents.

Connect a client

Any client that speaks MCP over HTTP works. Paste the URL, add the key as a header, done.

claude mcp add --transport http payle https://www.usepayle.com/mcp \
  --header "Authorization: Bearer payle_sk_…"

{
  "mcpServers": {
    "payle": {
      "type": "http",
      "url": "https://www.usepayle.com/mcp",
      "headers": {
        "Authorization": "Bearer payle_sk_…"
      }
    }
  }
}

{
  "mcpServers": {
    "payle": {
      "url": "https://www.usepayle.com/mcp",
      "headers": {
        "Authorization": "Bearer payle_sk_…"
      }
    }
  }
}

curl -s https://www.usepayle.com/mcp \
  -H "Authorization: Bearer payle_sk_…" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A key is the only credential. Create one below — it is shown once, so copy it somewhere safe.

Your connectors

One key per agent, so you can see which one asked for what — and revoke one without touching the others.

What an agent can do

Five tools: two read, three ask. Every ask ends on a page where you decide, in person.

• payle_accountread

  Reads the Payle account behind the key: handle, reserved card finish, Drop entry.

• payle_payask

  Asks to pay a merchant an exact amount, and returns a one-use link where you approve or decline.

• payle_payment_statusread

  Tells you what happened to one request: still waiting, approved, declined, expired.

• payle_paymentsread

  Lists what this key has asked for, so it does not ask twice.

• payle_cancel_paymentask

  Withdraws a request that is still waiting. Once you have decided, it stays decided.

Why this cannot spend on its own

• A person decides

  Every request ends on a Payle page that only the account holder can open. There is no setting that skips it, and no amount small enough to skip it.

• Ceilings on the key

  A cap per request and a monthly cap, both attached to the key. A request above a cap is refused by the database itself, not by the agent, and not by politeness.

• Optional merchant list

  A key can be locked to the merchants you name. Everything else is refused before it becomes a request.

• Keys are never stored readable

  Only a SHA-256 digest of the key is kept, so nobody — not even we — can read it back. Revoking it stops the agent on the next call.