Protected payments with a dispute window

endpoint

https://api.stabledrop.me/api/ap2/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is Protected payments with a dispute window live?

Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.

Is Protected payments with a dispute window free to use?

Yes — the hub reached it with no key and no payment.

What tools does Protected payments with a dispute window have?

6 tools: prepare_escrow_payment, payment_qr, settle_escrow_payment, check_escrow_payment, read_published_page, verify_escrow_receipt.

Is Protected payments with a dispute window safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• prepare_escrow_payment reads unknown never probed

  Work out where a payment must go, before anybody signs or sends anything. `seller` and `nominal_buyer` may each be a wallet address OR AN EMAIL ADDRESS — an email is converted to the wallet that person owns, so you never need to know a wallet to use this. The parties are checked against the sanctions lists before an address is given. If any of them is listed the answer is `error: sanctioned_party` with no address, and the payment cannot be made through this service. The same answer comes back for terms whose payment contract was already refused on sanctions grounds when its money arrived: its address is not handed out again. If the check cannot be done right now the answer is `error: service_unavailable` with `retryable: true` and no address; try again shortly. Returns the payment address these terms produce, and TWO ways to fund it. Both end at the same address holding the same money; they differ only in who sends the transaction. **Transfer it yourself.** Send the tokens to the address from any wallet — a browser wallet, a hardware wallet, an exchange withdrawal. Nothing to sign for us, and no `payer` needed, because the payment contract never asks who paid: it reads its own balance. Then call `settle_escrow_payment` with no signature and we create the payment contract around what is there. **Or let us relay it.** Pass `payer` and this returns an EIP-3009 authorization for them to sign. We broadcast it and pay the gas, so **the payer needs no gas at all**. This is the only one an agent can complete unattended, and the only one that needs a key anywhere. Either way the address is the same, because it is a pure function of the terms. That is also what makes the relayed form safe: the payer signs `to` as part of the authorization, committing to every term at once — alter any of them afterwards and the address moves and the signature stops matching. `amount` is in the TOKEN's base units (1 USDC = 1000000), because that exact figure is one of the terms the address derives from. `expiry_timestamp` is an absolute Unix time — when the dispute window closes. `0` settles instantly with no recourse. There is no default: "instant, deliberately" and "nobody said" are different, and a caller must not discover afterwards which one they got. `nominal_buyer` is who may dispute and receives a refund. For an agentic payment this should be the PERSON, not the agent — they are the one who will later read a report and decide whether to object. **`seller` and `nominal_buyer` may each be a wallet address OR an email address.** An email resolves to the wallet Privy holds for that person — made for them if they have never logged in — and the same email always resolves to the same wallet, so the address derived here is the one `settle_escrow_payment` derives too. The resolved wallets come back under `parties`. A seller given by email is paid into that wallet; they sign in with the email to reach it. `external_id` keeps two otherwise-identical payments apart, and is one of the terms the address derives from. **Leave it out and a unique one is generated.** That is the right default: two payments matching in seller, amount, maturity and buyer would otherwise derive to the SAME address, and funding the second sends money into the first payment contract — recoverable only after that one is claimed, and only to ITS buyer. ⚠️ PASS BACK THE `external_id` THIS RETURNS, not the one you sent. A generated one is only knowable from the result, and settle derives the address again from whatever it is given: a different id is a different address, and the money is at this one. Supply your own for the opposite behaviour — a checkout hash gives "one checkout, one payment contract", so re-presenting the same purchase returns the same address rather than a second. `description` is what the payment is FOR, in the buyer's own words — ask them for it rather than defaulting. It is what they will be looking at in the dashboard weeks later deciding whether to dispute, and "Protected payment" tells them nothing about which one this was. It does not affect the address, so it can be set freely here. `brand` is the white-label partner the payment is being made under, if any (the `?b=` id, e.g. `escrow-me`). It is recorded on the contract for attribution only: it does not affect the address, and a malformed one is ignored rather than refused. `product_name` is what is being bought, shown on both parties' dashboards. Display only, like `brand`. A seller or nominal buyer given by email is recorded with that email as well, so the payment contract shows to them the way a request made on the site does. ⚠️ 1 to 160 characters. Longer is refused HERE rather than at the chain, where the check happens after the money has already moved. `arbiter` is who decides a dispute. Leave it out for the default arbiter, which is almost always right. It is one of the terms the address derives from, so pass the same value to `settle_escrow_payment`.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798

  {
    "type": "object",
    "required": [
      "seller",
      "amount",
      "expiry_timestamp",
      "nominal_buyer"
    ],
    "properties": {
      "brand": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "The white-label partner the payment is made under, if any: the site's `?b=` id, e.g. escrow-me. Attribution only; does not affect the address."
      },
      "payer": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Wallet address (0x…) that will sign an EIP-3009 authorization for us to relay, gas-free. Omit when the payer transfers the tokens to the address themselves."
      },
      "amount": {
        "type": "integer",
        "description": "How much, in the token's base units: 1 USDC = 1000000, so 25 USDC is 25000000. One of the terms the payment address derives from."
      },
      "seller": {
        "type": "string",
        "description": "Who gets paid: a wallet address (0x…) OR an email address. An email is converted to the wallet that person owns, created for them if they have never signed in; the same email always gives the same wallet."
      },
      "arbiter": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Wallet address (0x…) of who decides a dispute. Omit for the default arbiter. One of the terms the address derives from, so pass the same value to both tools."
      },
      "description": {
        "type": "string",
        "default": "Protected payment",
        "description": "What the payment is for, in the buyer's own words, 1 to 160 characters, e.g. 'Logo design, final files'. Shown on the dashboard; does not affect the address."
      },
      "external_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Your own id for this payment, e.g. a checkout hash, so re-presenting the same purchase derives the same address. Omit and a unique one is generated; pass back the value this returns."
      },
      "product_name": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "What is being bought, e.g. 'Blue ceramic vase'. Shown on both parties' dashboards; display only."
      },
      "token_symbol": {
        "type": "string",
        "default": "USDC",
        "description": "The token to pay in, e.g. USDC. Must be one the service supports."
      },
      "nominal_buyer": {
        "type": "string",
        "description": "Who may dispute and receives any refund — the PERSON, not the agent: a wallet address (0x…) OR an email address. An email is converted to that person's wallet, created for them if they have never signed in."
      },
      "expiry_timestamp": {
        "type": "integer",
        "description": "When the dispute window closes, as an absolute Unix time in seconds, e.g. 1764547200. 0 settles instantly with no recourse. There is no default."
      }
    },
    "additionalProperties": false
  }

  arguments 98 lines copy
• payment_qr reads unknown never probed

  A scannable code for a payment request, so nobody retypes an address. Pass the `payment_uri` from `prepare_escrow_payment`. Returns a QR a phone wallet can scan, with the token, network, destination and amount already in it. Or pass its `share_with_payer.pay_link`, for a code that opens the payment on the site instead — what to hand someone who is being asked to pay, as the site's own requests do. ⚠️ A SEPARATE TOOL RATHER THAN PART OF `prepare`, because the two have different audiences. `prepare` answers a machine and has to stay parseable; an image in its result would make the structured fields something a client has to dig for. A person who needs the code asks for it. ⚠️ AND IT ENCODES THE URI, NOT THE BARE ADDRESS. A QR holding only an address leaves the amount and the token to be entered by hand, which is the part worth removing — a payment contract funded with the wrong figure is not the payment contract these terms derive to, and the money sits at an address nothing can deploy to.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "payment_uri"
    ],
    "properties": {
      "payment_uri": {
        "type": "string",
        "description": "The `payment_uri` prepare_escrow_payment returned, for a code a wallet scans; or its `share_with_payer.pay_link`, for a code that opens the payment page."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• settle_escrow_payment moves money unknown never probed

  Create the payment contract around the money and return a signed receipt. `seller` and `nominal_buyer` may be wallet addresses OR EMAIL ADDRESSES, exactly as in `prepare_escrow_payment`; an email converts to the same wallet it did there. Works both ways, and which one runs is decided by whether you pass a signature: **Already transferred it yourself** — omit `authorization` and `signature`. We check the address holds the amount and build the payment contract around what is there. If the transfer has not arrived it says so, and nothing is spent finding out. **Want us to relay it** — pass the payer's `authorization` and `signature`. We broadcast it and pay the gas, so the payer needs none. This process holds no key and signs nothing; it is handed a signature and carries it. Pass the terms exactly as they were prepared. They ARE the payment contract's address, so a single altered figure moves it — and with a signature, stops matching what the payer signed. `seller` and `nominal_buyer` may be wallet addresses or email addresses, as in `prepare_escrow_payment`; an email resolves to the same wallet it did there. ⚠️ `external_id` MUST BE THE ONE `prepare_escrow_payment` RETURNED. It generates one when you leave it out, and that generated value is only knowable from its result — send a different one and this derives a different address, while the money is at the first. ⚠️ `error: sanctioned_party` IS FINAL. A party scored above 0 on the sanctions check when the money arrived (or the payment contract was refused before): the money is frozen at its address, and nothing more may be paid into it. Do not retry and do not offer to pay again. ⚠️ The receipt reports what the seller will actually RECEIVE in `token_amount`, with the platform fee named beside it. That is less than the amount authorised, and the two reconcile: token_amount + creator_fee = amount. `brand` is the white-label partner, as in `prepare_escrow_payment`: attribution only, and ignored when malformed. `arbiter`, when one was passed to `prepare_escrow_payment`, must be passed here too: it is a term, and leaving it out derives the default arbiter's address instead.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192

  {
    "type": "object",
    "required": [
      "seller",
      "amount",
      "expiry_timestamp",
      "external_id",
      "nominal_buyer"
    ],
    "properties": {
      "brand": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "The white-label partner the payment is made under, if any: the site's `?b=` id, e.g. escrow-me. Attribution only; does not affect the address."
      },
      "amount": {
        "type": "integer",
        "description": "How much, in the token's base units: 1 USDC = 1000000, so 25 USDC is 25000000. One of the terms the payment address derives from."
      },
      "seller": {
        "type": "string",
        "description": "Who gets paid: a wallet address (0x…) OR an email address. An email is converted to the wallet that person owns, created for them if they have never signed in; the same email always gives the same wallet."
      },
      "arbiter": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Wallet address (0x…) of who decides a dispute. Omit for the default arbiter. One of the terms the address derives from, so pass the same value to both tools."
      },
      "signature": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "The payer's hex signature (0x…) over that authorization. Omit together with `authorization`."
      },
      "description": {
        "type": "string",
        "default": "Protected payment",
        "description": "What the payment is for, in the buyer's own words, 1 to 160 characters, e.g. 'Logo design, final files'. Shown on the dashboard; does not affect the address."
      },
      "external_id": {
        "type": "string",
        "description": "The external_id prepare_escrow_payment returned, exactly. A different id derives a different address while the money sits at the first."
      },
      "token_symbol": {
        "type": "string",
        "default": "USDC",
        "description": "The token to pay in, e.g. USDC. Must be one the service supports."
      },
      "authorization": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": true
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "The EIP-3009 authorization object prepare_escrow_payment returned for the payer, unchanged. Omit when the payer transferred the tokens themselves."
      },
      "nominal_buyer": {
        "type": "string",
        "description": "Who may dispute and receives any refund — the PERSON, not the agent: a wallet address (0x…) OR an email address. An email is converted to that person's wallet, created for them if they have never signed in."
      },
      "expiry_timestamp": {
        "type": "integer",
        "description": "When the dispute window closes, as an absolute Unix time in seconds, e.g. 1764547200. 0 settles instantly with no recourse. There is no default."
      }
    },
    "additionalProperties": false
  }

  arguments 92 lines copy
• check_escrow_payment reads unknown never probed

  What has happened to a settled payment, from the `status_url` on its receipt.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "status_url"
    ],
    "properties": {
      "status_url": {
        "type": "string",
        "description": "The `status_url` on the receipt settle_escrow_payment returned, as is."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• read_published_page reads unknown 7h ago

  Read one of the published pages, for answering questions about how any of this works. Use it rather than guessing. What the fees are, how a dispute is decided and who decides it, what a buyer is agreeing to — all of it is written down, and none of it is safe to invent. how-it-works How an protected payment works, start to finish faq Common questions about protected payments, fees, disputes and timing arbitration-policy How a dispute is decided, by whom, and on what evidence terms-of-service The terms a buyer and seller are agreeing to privacy-policy What is collected and why plugins The WordPress and Shopify integrations home What the product is and who it is for

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "page"
    ],
    "properties": {
      "page": {
        "type": "string",
        "description": "Which page: how-it-works, faq, arbitration-policy, terms-of-service, privacy-policy, plugins or home."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• verify_escrow_receipt reads unknown 7h ago

  Check a receipt's signature against the key its issuer publishes. ⚠️ THE KEY IS FETCHED FROM THE RECEIPT'S OWN `iss`, NOT FROM WHOEVER HANDED IT OVER. Otherwise anything that can serve a receipt can also serve the key that vouches for it, and the signature stops meaning anything. Use this on receipts from anywhere, including ones this server did not produce.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "payment_receipt"
    ],
    "properties": {
      "payment_receipt": {
        "type": "string",
        "description": "The receipt as a compact JWS string (header.payload.signature), e.g. the `payment_receipt` settle_escrow_payment returned, or one from anywhere else."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.