FEELESS · NO KYC · NON-CUSTODIAL · KEEP 100% · FEELESS · NO KYC · NON-CUSTODIAL · KEEP 100% ·

Non-custodial · Feeless Read the MCP docs →

        
        For AI agents & LLMs
      

The payment processor your AI sets up in one sentence.

Tell your assistant where the money goes. It calls Shieldz over MCP and hands back a live payment link, an embed, and a QR. No dashboard. No API key. No account.

Start free $0 Read the MCP docs

        ↳ keyless
        ↳ non-custodial · funds never touch us
        ↳ OFAC-screened
        ↳ EVM · BTC · ZEC
      

01 / THE FLOW

One message in. A working checkout out.

your assistant · shieldz mcp connected

Take USDC payments to 0x71C…3F2 on Base, $49 each.

Done, screened the address, created a hosted checkout. Here's your link:

PAY LINK · INVOICE · $49.00

shieldz.cash/p/8kQ2x

Copy link Embed

Say where funds go

An address and a chain, the only required input. That's the whole "setup".

Agent calls Shieldz

Over MCP, keyless. We screen the address, create a persistent address-bound checkout, return the link.

Share & get paid

Link, embed snippet, and QR, instantly. Funds settle straight to the address. We never custody a cent.

02 / @shieldz/mcp

Three tools your agent already knows how to call.

No pre-issued key needed. Add the server, and the agent can monetize with nothing but an address. Power users still drop in a SHIELDZ_API_KEY for the full merchant tools.

@shieldz/mcp · create_payment_link

// no API key, identity is the settlement address
create_payment_link({
  address: "0x71C…3F2",
  chain:   "base",
  asset:   "USDC",
  amount_usd: 49,
  memo:    "Pro plan"
})

→ {
  pay_url: "https://shieldz.cash/p/8kQ2x",
  qr_url:  "…/p/8kQ2x.png",
  embed:   "<script src=…>",
  manage_url: "…/a/cap_8kQ2x"
}

create_payment_link()

One-time, fixed-amount invoice. Returns link + embed + QR.

create_tip_jar()

Reusable link, payer picks the amount. Pay it any number of times, monetize anything.

get_account_status()

Read paid vs pending and totals back out, so the agent can report results to you.

03 / RUNS IN YOUR AGENT

Built for the agents people actually run.

Shieldz ships as a single MCP server. Drop it into any autonomous agent and it can take payments, no key handed over, nothing custodial.

OpenClaw

214k★ · local-first · messaging

Add Shieldz as a skill from ClawHub. Text your agent an address on WhatsApp or Telegram and a live link comes straight back.

claw skill add @shieldz/mcp

AutoGPT

173k★ · task platform

Register the Shieldz MCP block in your agent graph. It monetizes a task's output, invoice or tip jar, without ever holding a key.

block: shieldz/payment_link

Manus

general autonomous agent

Connect the Shieldz MCP server once. Manus drops a checkout link into any workflow it runs, from a freelance deliverable to a paywall.

mcp add shieldz.cash/mcp

Hermes

Nous Research · self-improving

Hermes' skills-and-memory loop picks up Shieldz as a tool, it learns to monetize a workflow once and reuses the link the next time around.

tool: shieldz.payment_link

Goose

Block · MCP-native

Goose is built on MCP, so Shieldz is a one-line extension. Ask it to bill for a task and it hands back a checkout, no key in the config.

goose mcp add shieldz

Devin

Cognition · autonomous SWE

Have Devin ship the feature and charge for it in the same run, it calls Shieldz to mint the payment link, keyless and non-custodial.

mcp: @shieldz/mcp

↳ Any MCP-capable agent works, Claude, Cursor, AutoGen and the rest included.

04 / SPOTLIGHT · OpenClaw

Your OpenClaw agent gets paid while you sleep.

OpenClaw runs on a heartbeat and lives in your chat apps. With the Shieldz skill it spins up a payment link from a single message, keyless, non-custodial, then reports what came in on its next cycle.

          $ claw skill add @shieldz/mcp
        

✓ No key, the address is the identity

✓ Reports earnings on every heartbeat

✓ Works from WhatsApp, Telegram & iMessage

OpenClaw · Telegram

spin up a tip jar for my newsletter, USDC on Base

Done, screened it, created a reusable tip jar.
shieldz.cash/p/t/9b2
Pinned it for you. I'll report tips each heartbeat.

HEARTBEAT · 14:00,3 new tips, +$36 today

Goose

Block · MCP-native

Bills for the task it just ran.

goose › task complete, invoicing
$ shieldz.payment_link --usd 120
→ shieldz.cash/p/Gk7

↳ Native MCP, one extension, no key in config.

Devin

Cognition · autonomous SWE

Ships the feature, then charges for it.

✓ PR #482 merged · feature/paywall
→ mint shieldz link for access
→ shieldz.cash/p/Dv9 · $29/mo

↳ Same run: build, deploy, monetize.

05 / GUARDRAILS

Keyless, not careless.

Anyone can create a link, so every link passes the same checks, and because nothing is custodial, the worst case is never lost funds.

SCREEN

OFAC sanctions check

Every settlement address is matched against the OFAC SDN crypto list before a link exists. A hit → blocked, logged.

THROTTLE

Velocity limits

Per-IP, per-address, and global ceilings. Abuse hits a 429 with Retry-After, the SDKs back off for you.

CUSTODY

Funds never touch us

Money settles straight to the address you named. Even fully abused, there is nothing of yours for us to lose.

TRANSPARENT

Visible destination

The checkout always shows who's being paid, so a payer sees exactly where their money lands.

06 / IT REPORTS BACK

Your agent sets it up, and watches it.

Creation also returns a capability-token view: a clean page a human can open with no login, and a JSON twin an agent can fetch. The token in the URL is the access.

“You've received $1,840 across 12 payments.”

Attach an email or Sign-In with Ethereum
later → full dashboard, webhooks, real keys. No KYC.

GET /a/cap_8kQ2x9f.json

{
  "settlement": {
    "chain": "base",
    "asset": "USDC",
    "address": "0x71C…3F2"
  },
  "links": 3,
  "invoices": { "paid": 12, "pending": 1 },
  "totals_usd": 1840.00,
  "claimed": false
}

Set up payments in one sentence.

Keyless, non-custodial, OFAC-screened. The payment processor your AI configures while you keep talking.

Start free $0 Read the MCP docs

ShieldZ