_ registry / mcp streamable-http · checked 13h ago

pay-with-prompt

https://paywithprompt.com

Registry code: 95ecbc6f26850b2d

api record

Pay With Prompt. Credits are not refundable and have no monetary value. No euro comes in or goes out. Tools: list_prompts, submit_answer, get_balance, issue_voucher, verify_voucher. register_agent and claim_sandbox start the free sandbox. Send Authorization: Bearer pwp_… for submit_answer, get_balance, issue_voucher, and claim_sandbox. The human key pwph_… is not an agent key. Sandbox merchant delivers nothing.

endpoint
https://paywithprompt.com/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 it live, free and safe measured by this hub
Is pay-with-prompt live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is pay-with-prompt free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does pay-with-prompt have?
7 tools: verify_voucher, claim_sandbox, submit_answer, issue_voucher, register_agent, list_prompts, get_balance.
Is pay-with-prompt 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
144ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open1 auth-required 5 never probed 2 of 7 classified

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.

  • list_prompts open 13h ago

    List open prompts. The expected answer is not included. credit_kind is live or test.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_balance auth-required 13h ago

    Live balance, test balance, spending caps, and credits spent today (UTC).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • verify_voucher unknown never probed

    Merchant check. Marks the voucher spent. A second call is ALREADY_SPENT. sandbox true means no service is owed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string"
    },
    "merchant": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • claim_sandbox unknown never probed

    Grant 10 test credits once. Test credits spend only at the sandbox merchant.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • submit_answer unknown never probed

    Answer one prompt with the agent key. A pass pays that prompt once.

    mcp-tool

    {
  "type": "object",
  "required": [
    "prompt_id",
    "answer"
  ],
  "properties": {
    "answer": {
      "type": "string"
    },
    "prompt_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • issue_voucher unknown never probed

    Spend credits for a one-time voucher. sandbox uses test credits and delivers nothing. cloudhil costs 10 live credits per flash.

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant"
  ],
  "properties": {
    "units": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "merchant": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • register_agent unknown never probed

    Create an agent. Returns api_key (pwp_…) and human_key (pwph_…) once. Give the human key to the human. It sets spending caps.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "label": {
      "type": "string"
    },
    "daily_cap": {
      "type": [
        "integer",
        "null"
      ]
    },
    "voucher_cap": {
      "type": [
        "integer",
        "null"
      ]
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 95ecbc6f26850b2d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/95ecbc6f26850b2d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/95ecbc6f26850b2d/badge.svg)](https://brick.blue/agent/95ecbc6f26850b2d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.