veyra

endpoint

https://veyra.money/api/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 veyra live?

Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.

Is veyra free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does veyra have?

7 tools: cancel_payment, list_payments, list_payment_sources, create_payment, get_payment, get_capabilities, get_budget.

Is veyra 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.

• cancel_payment changes data auth-required never probed

  Cancel a payment only while still cancellable.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "payment_id"
    ],
    "properties": {
      "payment_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 12 lines copy
• list_payments reads auth-required never probed

  List this agent's recent payments.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number"
      }
    },
    "additionalProperties": false
  }

  arguments 9 lines copy
• list_payment_sources reads auth-required never probed

  List masked payment sources available to this agent, including whether each can settle unattended. Never request secrets.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• create_payment moves money auth-required never probed

  Create a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status `confirmed` means value moved on-chain and `tx_ref` on get_payment is the transaction you can show the recipient as proof; `confirmed_simulated` means it settled on the simulated rail and NO real money moved — never report that to the user as a real payment, and never offer its reference as proof of one. If status is awaiting_approval, give the user next_action.url; when `simulated` is true that link is a single click, otherwise it asks them to sign an on-chain USDC transfer in their own wallet — either way do not ask them to log into Veyra, and do not retry while it is pending. NEVER create a second payment because you are unsure the first worked: call get_payment or list_payments and read its status. Reuse the same idempotency_key for a retry of the same payment; a new key means a genuinely new payment and will spend again.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "required": [
      "amount",
      "asset",
      "recipient",
      "network",
      "reason",
      "idempotency_key"
    ],
    "properties": {
      "asset": {
        "type": "string",
        "description": "e.g. USDC"
      },
      "amount": {
        "type": "string",
        "description": "Decimal string, e.g. 4.50"
      },
      "reason": {
        "type": "string"
      },
      "network": {
        "type": "string",
        "description": "e.g. base"
      },
      "recipient": {
        "type": "string",
        "description": "Destination address. Must be a valid address for the network, e.g. 0x… on base."
      },
      "idempotency_key": {
        "type": "string",
        "description": "Agent-generated unique key; retries must reuse it"
      }
    },
    "additionalProperties": false
  }

  arguments 37 lines copy
• get_payment reads auth-required never probed

  Get canonical state for one payment request, including which rail settled it and, once confirmed on a real rail, `tx_ref` — the on-chain transaction — plus `explorer_url`. This is how you verify a payment actually completed, and what you show a recipient as proof. Always call this before concluding a payment failed.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "payment_id"
    ],
    "properties": {
      "payment_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  }

  arguments 12 lines copy
• get_capabilities reads auth-required 14h ago

  Return the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist. Read-only.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_budget reads auth-required 14h ago

  Return remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 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.