Documentation

Veyra is a non-custody permission layer. You connect wallets, set how much an agent may spend, and get one MCP URL. Agents call tools like create_payment — they never receive seed phrases or private keys.

• Sign up and verify your email.
• Connect at least one wallet (MetaMask, Base/Coinbase passkey, or WalletConnect for Base USDC).
• Create an MCP endpoint with per-tx / daily limits and auto / ask bands.
• Paste the URL + bearer token into Claude, Cursor, or Codex.

Remote endpoint: POST /api/mcp with header Authorization: Bearer veyra_…

Example Cursor / Claude Desktop config:

{
  "mcpServers": {
    "veyra": {
      "url": "https://your-host/api/mcp",
      "headers": {
        "Authorization": "Bearer veyra_…"
      }
    }
  }
}

Rotate or revoke credentials anytime from the endpoint page in the dashboard.

• get_capabilities / get_budget — policy summary (read-only)
• list_payment_sources — masked sources only
• create_payment — amount, asset, recipient, network, reason, idempotency_key
• get_payment / list_payments / cancel_payment

Payments under auto-max can proceed without a human prompt (still subject to limits). Amounts in the ask band return awaiting_approval with a one-time link. Over the ask band or daily cap → blocked.

Approval links ask the bound wallet to send a real USDC transfer on Base. Rejecting in the wallet cancels the payment. No Veyra login is required on the approve page — auth is the secret token + matching wallet + on-chain receipt.

When approval is required, Veyra emails the account owner and (if enabled) sends a browser push that opens the approve URL. WalletConnect can also ping the mobile wallet when you open that link.

Current rail focus: USDC on Base via connected EVM wallets. Phantom (Solana) can be linked for identity, but on-chain approve transfers use MetaMask / Base / Coinbase / WalletConnect.