Vaaya is a procurement gateway for agents: instead of holding a crypto\nwallet and a private key (x402 style) or juggling one API key per vendor, your\nagent talks to a single MCP server — https://vaaya.ai/mcp — and buys\ncapabilities pay-per-call from one prepaid balance.
\nWhat that buys you, through one endpoint:
\nHow it differs from the x402 skills you may have seen:
\nAn agent can open its own account with two POSTs — no human at the keyboard:
\nRegister an OAuth client (dynamic client registration, no pre-approval):
\nPOST https://vaaya.ai/oauth/register\nContent-Type: application/json\n\n{ \"client_name\": \"openclaw-agent\", \"grant_types\": [\"refresh_token\"] }\nDo not omit grant_types — the default is the authorization_code grant,\nwhich then requires redirect_uris.
Create the account with the client_id you just received:
POST https://vaaya.ai/api/v1/signup/agent\nContent-Type: application/json\n\n{ \"client_id\": \"...\" }\nThe response contains an access_token + refresh_token, a $1 starter\ncredit (spendable immediately, expires in 24h), and a claim_url.
Store the refresh_token and user_id in your persistent memory or\nconfig NOW and reuse them across sessions. Never re-register —\nre-registering forfeits your history and grants no new credit.
Hand claim_url to your human when they're around. One Google sign-in\nmerges the account into theirs. Once they add a card, a $2 welcome credit\nline activates — the card settles only what agents actually spend — and\nconnecting GitHub grows the line from their track record. Prepaid credit\npacks are available at https://vaaya.ai/credits. Claim links expire in\n24h — never memorize one; mint a fresh link anytime via\nGET https://vaaya.ai/api/v1/signup/claim-url (bearer auth).\nYour tokens keep working across the merge.
openclaw mcp add vaaya --url https://vaaya.ai/mcp --transport streamable-http --auth oauth\nopenclaw mcp login vaaya\nlogin opens a browser for the OAuth approval (sign-in with Google). If you\nsigned up agent-first (above), the account already exists — the human claim\nvia claim_url links it to their Google identity. No API keys are ever\npasted anywhere; the grant is revocable at https://vaaya.ai/connected-apps.
Always start with consult. You never need to know service names, params,\nURLs, or keys — consult knows the live catalog and hands back the exact call.
consult({ intent }) — describe the whole goal in plain English\n(\"make a 10s product demo clip from these screenshots\"). It returns either\na question to relay to your user (mode: \"converse\"), or mode: \"call\"\nwith an ordered list of ready-to-run calls\n{ service, action, params, max_cost_cents, why }.use({ service, action, params, max_cost_cents }) — execute one call\nexactly as consult handed it to you. Bills on success only. Long-running\nwork returns { async: true, job_id }.result({ job_id }) — poll async jobs. Never re-run use to check on\na job — that starts a new, separately-billed job.consult again with a one-line outcome for\nresult-aware next steps.Sandboxes (session / close) bill per second of uptime — always close\nwhen done.
max_cost_cents with every planned call, and\nyou pass that cap into use — the call can never charge more than the cap.use responses report exactly what was\ncharged (charged_cents) and what remains (balance_remaining_cents).credits_required), do not\nretry — relay the returned credits_url to your user.