Skip to main content

​
Overview

OpenClaw agents browse the web through the Browser Relay (CDP on port 18792). When your agent reaches a checkout page, Ovra takes over the payment — the agent never sees card data.

​
Setup

​
1. Add Ovra MCP Server

In your OpenClaw config, add Ovra as an MCP server: 
{
  "mcpServers": {
    "ovra": {
      "type": "streamable-http",
      "url": "https://api.getovra.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_test_..."
      }
    }
  }
}
Your agent now has access to 29 payment tools.

​
2. Agent Flow

The agent handles the entire flow autonomously: 
Agent: "Buy a USB-C hub on amazon.de for under €30"

1. Agent browses amazon.de → finds product → adds to cart → goes to checkout
2. Agent calls: ovra_intent_create({ agentId, purpose: "USB-C Hub", expectedAmount: 29.99 })
3. Ovra checks policy → auto-approved
4. Agent calls: ovra_checkout_pay({ intentId: "in_xxx", cdpUrl: "ws://localhost:18792" })
5. Ovra fills the payment form via Browser Relay — agent sees nothing
6. Agent receives: { success: true }
7. Agent confirms the order

​
Key MCP Tools

ToolWhat it does
ovra_agent_createCreate an agent with virtual Visa card
ovra_agent_fundAdd funds to agent wallet
ovra_intent_createDeclare a purchase intent (policy auto-checks)
ovra_checkout_payFill payment form via CDP — agent never sees card data
ovra_intents_listCheck intent status
ovra_policy_simulateTest if a purchase would be allowed

​
How the Agent Decides to Pay

The agent knows when to call Ovra because:
  1. It recognizes a payment form on the page (card number fields, “Pay” button)
  2. The MCP tool description tells it: “fill card — agent never sees PAN/CVV”
  3. The agent creates an intent first, then calls checkout
No special prompting needed — the MCP tool descriptions guide the agent naturally.