MCP-Server
Vaaya
ai.vaaya/mcp
Was dieses MCP kann
Provides paid access to external services, user purchases, sandbox execution, LLM calls, and tokenized stock trading funded through Vaaya.
Funktionen
Tools
13
Tools
buy
Buy Something for the User
Find and buy products, tickets, bookings and subscriptions for the user at supported stores. Start with `search` { query } to find the item and merchant page using Vaaya OneSearch (5¢ per search); the user can describe what they need without supplying a link. Before checkout, use `setup` to check payment and shipping readiness; resolve missing setup once. Persistent merchant accounts are managed at /store-connections. Use store_connection_id to select an account. Passwords and verification codes belong only on the merchant page, never in chat. PRODUCT DISCOVERY: if the user describes what to buy but provides no URL, use `search` { query: <product, variant, budget and preferred merchant if specified> } to locate it under the existing tool spending permissions; do not ask them to paste a link or say search for it first. Search is not purchase authorization. Respect search fees and spending limits; if search is unavailable, explain the actual error and then ask for a link. Verify the merchant, item and variant from the result; ask only when matches are ambiguous or details cannot be verified. Never invent a product URL, final total or delivery date from a search snippet. THE SEAMLESS PATH: once the user has told you what to buy and you have the exact item, merchant page URL and total, call `purchase` { item, merchant, url, total_cents, confirmed: true, confirmation: <the user's own words> } — it approves from their message (under the chat limit), starts buying in the user's cloud browser in the background and returns `message` ("Hold on — buying it now."): RELAY IT, then poll `status` { approval_id } every ~10 seconds and relay its `message` when the status is completed ("Done — …"), requires_action (read action_required.reason for the exact blocker) or failed. If `status` says the user's shipping address is missing, ask for it and call `address` { name, line1, line2?, city, state?, postal_code, country, phone? } then `checkout` { approval_id } to resume; if merchant authentication is pending, relay handoff_url and handoff_deadline. The durable worker checks authentication and resumes the same authorized purchase automatically. Do not ask the user to send done or submit codes in chat. If the handoff expires, relay the recovery page; it does not clear order or payment uncertainty. Other sub-commands: `search` { query } (protocol merchants plus a real web search; the web half bills 5¢), `propose` { item, merchant, total_cents, url?, notes?, confirmed?, confirmation? } (creates an approval; without `confirmed` it returns an approval link the user opens — show its `message` VERBATIM), `checkout` { approval_id, params? } (buys an approved purchase; for a browser merchant it runs in the background like `purchase`). Use the user's existing authorization of the exact item and total; do not ask them to confirm twice. Ask only for missing purchase details. Nothing is ever bought without the user's yes: `checkout` refuses anything else. Use `reconcile` { approval_id } after an uncertain submission: it only inspects the existing checkout and never submits payment. For an unavailable checkout or inconclusive reconciliation, relay recovery_url and recovery_instructions from status. The user can resolve the attempt on its approval page only after checking both merchant orders and payment records. A chat statement alone does not clear the lock, and expiration does not clear it. If status or replay says purchase_resolved, never reuse checkout on that approval. When the user requests another attempt, call propose with retry_of set to that resolved ID, current item/price and no confirmed flag, then show the new approval link. Check setup browser_allowance first; a daily_browser_limit requires waiting until resets_at, not reconnecting or changing request text. For a handoff, return action_required.url and the deadline. The user fixes 2FA, CAPTCHA, payment, address or booking issues on that authenticated page and uses Return control to Vaaya; do not call checkout to bypass a pending handoff. Status polling never creates a replacement. Resume only the same approval_id; do not recreate a purchase to bypass an unresolved attempt. `charged_cents` is the Vaaya tool fee, NOT a merchant charge; read merchant_payment separately, and never infer a hold or capture from Link approval. Never open `browserbase` sessions yourself to buy something — only `buy` can.
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['command'], 'properties': {'url': {'type': 'string', 'description': 'The exact product page the item came from — the driver starts there (`purchase`, `propose`).'}, 'city': {'type': 'string', 'description': 'City (`address`).'}, 'item': {'type': 'string', 'description': "What exactly is being bought, in the user's words — variant, size, quantity (`purchase`, `propose`)."}, 'name': {'type': 'string', 'description': 'Full name for shipping (`address`).'}, 'email': {'type': 'string', 'description': 'Contact email for the order; defaults to the account email (`address`).'}, 'line1': {'type': 'string', 'description': 'Street address (`address`).'}, 'line2': {'type': 'string', 'description': 'Apartment / unit (`address`).'}, 'notes': {'type': 'string', 'description': 'One line for the driver/user: variant, size, colour, quantity, delivery window.'}, 'phone': {'type': 'string', 'description': 'Contact phone for delivery (`address`).'}, 'query': {'type': 'string', 'description': 'Describe the product, variant, budget and preferred store if any. `search` uses OneSearch to find matching items and merchant pages (5¢).'}, 'state': {'type': 'string', 'description': 'State / region (`address`).'}, 'params': {'type': 'object', 'description': "The merchant's own purchase body (product id, quantity, email, shipping) for a protocol merchant (`purchase`, `checkout`).", 'additionalProperties': True}, 'booking': {'anyOf': [{'type': 'object', 'required': ['kind', 'travelers', 'segments', 'baggage', 'changeCancellationTerms'], 'properties': {'kind': {'type': 'string', 'const': 'flight'}, 'baggage': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'segments': {'type': 'array', 'items': {'type': 'object', 'required': ['origin', 'destination', 'departureDate', 'departureTime', 'flightNumber', 'cabin', 'fare'], 'properties': {'fare': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'cabin': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'origin': {'type': 'string', 'pattern': '^[A-Z]{3}$'}, 'destination': {'type': 'string', 'pattern': '^[A-Z]{3}$'}, 'flightNumber': {'type': 'string', 'maxLength': 500, 'minLength': 1}, 'departureDate': {'type': 'string', 'pattern': '^\\d{4}-\\d{2}-\\d{2}$'}, 'departureTime': {'type': 'string', 'pattern': '^([01]\\d|2[0-3]):[0-5]\\d$'}}, 'additionalProperties': False}, 'maxItems': 8, 'minItems': 1}, 'travelers': {'type': 'integer', 'maximum': 9, 'minimum': 1}, 'changeCancellationTerms': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}}, 'additionalProperties': False}, {'type': 'object', 'required': ['kind', 'property', 'address', 'checkIn', 'checkOut', 'rooms', 'adults', 'children', 'roomType', 'ratePlan', 'cancellationTerms', 'paymentTiming', 'mandatoryFeesCents'], 'properties': {'kind': {'type': 'string', 'const': 'hotel'}, 'rooms': {'type': 'integer', 'maximum': 9, 'minimum': 1}, 'adults': {'type': 'integer', 'maximum': 30, 'minimum': 1}, 'address': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'checkIn': {'$ref': '#/anyOf/0/properties/segments/items/properties/departureDate'}, 'checkOut': {'$ref': '#/anyOf/0/properties/segments/items/properties/departureDate'}, 'children': {'type': 'integer', 'maximum': 30, 'minimum': 0}, 'property': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'ratePlan': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'roomType': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'paymentTiming': {'enum': ['pay_now', 'pay_at_property', 'deposit'], 'type': 'string'}, 'cancellationTerms': {'$ref': '#/anyOf/0/properties/segments/items/properties/flightNumber'}, 'mandatoryFeesCents': {'type': 'integer', 'minimum': 0}}, 'additionalProperties': False}], '$schema': 'http://json-schema.org/draft-07/schema#', 'description': 'Required for Expedia flights and Booking.com hotels: exact itinerary/stay, counts, fare/room, baggage/cancellation and payment terms. These are shown for approval and cannot be substituted. Traveler identity documents are entered directly on the merchant page, never in chat. Final booking review requires the authenticated handoff page.'}, 'command': {'enum': ['setup', 'search', 'purchase', 'propose', 'status', 'checkout', 'reconcile', 'address', 'credentials'], 'type': 'string', 'description': 'Use `search` to find an item with OneSearch, `purchase` to buy an authorized item, and `status` to track it.'}, 'country': {'type': 'string', 'description': 'Two-letter country code, e.g. US (`address`).'}, 'currency': {'type': 'string', 'description': "ISO currency, default 'usd'."}, 'merchant': {'type': 'string', 'description': 'Merchant host or URL, e.g. bombas.com (`purchase`, `propose`, `credentials`).'}, 'password': {'type': 'string', 'description': 'Password at the merchant — stored encrypted, never returned (`credentials`).'}, 'retry_of': {'type': 'string', 'format': 'uuid', 'description': 'For propose only: the previous approval ID resolved by the owner as no order/payment. Use only when the user requests a new attempt; omit confirmed and show the fresh approval link. Never vary item text or confirmation to bypass replay or locks.'}, 'username': {'type': 'string', 'description': 'Email/username at the merchant (`credentials`).'}, 'confirmed': {'type': 'boolean', 'description': 'true when the user has said yes to this exact item and total in the conversation (`purchase`, `propose`).'}, 'approval_id': {'type': 'string', 'description': 'The approval returned by purchase/propose (`status`, `checkout`).'}, 'postal_code': {'type': 'string', 'description': 'Postal / ZIP code (`address`).'}, 'total_cents': {'type': 'number', 'description': 'The full total the user will pay, in cents (`purchase`, `propose`).'}, 'confirmation': {'type': 'string', 'description': "The user's own words approving it, verbatim (`purchase`, `propose`)."}, 'store_connection_id': {'type': 'string', 'description': 'Merchant account connection ID from /store-connections. Required when multiple accounts are connected to the same store. Sign in and enter verification codes directly on that page, never in chat.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'web': {'description': 'Web search evidence, when `search` ran one.'}, 'item': {'type': 'string', 'description': 'What is being bought.'}, 'next': {'type': 'string', 'description': 'The next call to make.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'status': {'type': 'string', 'description': 'proposed | approved | declined | checking_out | requires_action | completed | failed | expired.'}, 'command': {'type': 'string', 'description': 'Which sub-command ran: setup | search | purchase | propose | status | checkout | reconcile | address | credentials.'}, 'message': {'type': 'string', 'description': 'What to show the user — relay it VERBATIM.'}, 'receipt': {'type': 'object', 'description': 'What was bought, once it completes.'}, 'card_url': {'type': 'string', 'description': 'Where the user adds a card, when they have none yet.'}, 'currency': {'type': 'string', 'description': 'ISO currency of total_cents.'}, 'merchant': {'type': 'string', 'description': 'Who it is being bought from.'}, 'login_url': {'type': 'string', 'description': 'Live View link for the user to sign into their own merchant account.'}, 'merchants': {'type': 'array', 'description': 'Protocol merchants that sell this kind of thing.'}, 'expires_at': {'type': 'string', 'description': 'When the approval stops being valid (24h from proposal).'}, 'approval_id': {'type': 'string', 'description': 'The purchase approval this call is about.'}, 'total_cents': {'type': 'number', 'description': "The user's total, in cents — paid by their own card, not the balance."}, 'approval_url': {'type': 'string', 'description': 'Where the user approves — relay it.'}, 'billing_note': {'type': 'string', 'description': 'Explains the separation of tool fees and merchant payments.'}, 'order_status': {'type': 'string', 'description': 'confirmed | not_confirmed | unknown | absent_user_reported.'}, 'card_required': {'type': 'boolean', 'description': 'True when a card must be added before this purchase.'}, 'charged_cents': {'type': 'number', 'description': 'Amount billed for this call, in cents.'}, 'live_view_url': {'type': 'string', 'description': 'Live View link to the browser doing the checkout.'}, 'payment_source': {'type': 'string', 'description': 'merchant_saved_card | link_card, once checkout picks one.'}, 'relay_verbatim': {'type': 'boolean', 'description': 'True when `message` must be shown to the user as written.'}, 'tool_fee_cents': {'type': 'number', 'description': 'Vaaya buy tool-call fee. Not a merchant charge.'}, 'action_required': {'description': 'Null or an object with reason, message and optional action URL.'}, 'approval_status': {'type': 'string', 'description': 'Stored approval state; needs_login is the legacy name for any pause.'}, 'merchant_payment': {'type': 'object', 'description': 'Merchant payment status and charged_cents, null when unverified. Separate from the tool fee.'}}, 'additionalProperties': True}
close
Close a Sandbox Session
Close an E2B sandbox session and stop its billing. Pass the `session_id`. Captures the final metered uptime cost and releases the hold. ALWAYS call this when finished with a session — an open session keeps billing per second of uptime. Safe to call repeatedly (idempotent).
Idempotent
Eingabeschema
{'type': 'object', 'required': ['session_id'], 'properties': {'session_id': {'type': 'string', 'description': 'The session_id to close.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'status': {'type': 'string', 'description': 'Final session state.'}, 'session_id': {'type': 'string', 'description': 'The closed session id.'}, 'charged_cents': {'type': 'number', 'description': 'Total metered uptime cost, in cents.'}, 'balance_remaining_cents': {'type': 'number', 'description': 'Wallet balance remaining, in cents.'}}, 'additionalProperties': True}
consult
Consult Vaaya — Plan Any Capability
Vaaya's consultant. Describe ANY external capability you or the user might want — generate an image/video, search or scrape the web, run code in a sandbox, send/receive email, enrich a contact — and it helps figure out the best way, teaching the user what Vaaya can do. It is CONVERSATIONAL and remembers prior turns. It returns: mode='converse' (a reply to RELAY to the user verbatim — questions, options, ideas; get the user's response and call consult again with it, so the conversation continues), mode='call' (an ordered list of calls to run via `use`, with a message explaining the preferred choice + alternatives + why; multi-step results may contain placeholders like '<from step 1: sandbox_id>' — run earlier steps first and substitute), or mode='unsupported'. Every reply includes `suggestions` (2-3 things to do next) — surface these to the user. AFTER you run a `call` result's calls via `use`, call consult ONE more time with a short note on the outcome (what was produced / any failures) — it returns result-aware, Vaaya-grounded next steps to offer the user (the `call` result's `after_running` field reminds you). Call consult whenever you hit a capability gap or the user wants to know what's possible. It does NOT execute or bill — you run returned calls via `use`. ALWAYS show the user consult's `message` and `suggestions` and let them steer.
Nur Lesen
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['intent'], 'properties': {'intent': {'type': 'string', 'description': 'Plain-English description of what you want, or your answer to a previous clarify question. Be concrete — include the prompt text, URL, budget, or target the task implies.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'mode': {'enum': ['converse', 'call', 'unsupported'], 'type': 'string', 'description': "How to proceed: relay 'converse', run 'call', or report 'unsupported'."}, 'calls': {'type': 'array', 'description': 'Ordered list of { service, action, params, max_cost_cents, why } to run via `use`.'}, 'reason': {'type': 'string', 'description': "Why the request is unsupported (mode='unsupported')."}, 'message': {'type': 'string', 'description': "Consultant's reply — relay to the user verbatim."}, 'run_with': {'type': 'string', 'description': 'Which tool to execute the calls with.'}, 'suggestions': {'type': 'array', 'description': '2-3 suggested next steps to surface to the user.'}, 'after_running': {'type': 'string', 'description': 'Reminder to call consult again with the outcome.'}, 'if_tools_missing': {'type': 'string', 'description': 'What to do when a named first-party tool (gtm_*, worker_*, …) is missing from your tool list: it was just unlocked — refresh the tool list; never improvise a fallback.'}, 'if_use_unavailable': {'type': 'string', 'description': 'What to do when the `use` tool is missing from your tool list — relay to the user.'}}, 'additionalProperties': True}
docs
Read Vaaya Deep Reference
Vaaya's deep reference, FREE and instant. Pass `topic` to get the full playbook for a capability area — exact services, actions, params, prices, model lists, and gotchas — the same reference files the vaaya skill ships. Topics: 'setup' (connecting an agent, a chat app, or an unattended process), 'tools' (exact params of every Vaaya tool, GTM suite included), 'media' (image/video/audio models + product-demo videos), 'gtm' (leads, enrichment, outreach, signals, email), 'research' (OneSearch lanes, deep research, company/market research playbooks), 'data' (scraping, people, social platforms, public records, onchain, compliance), 'compute' (sandboxes, browser automation, files, memory, workers, phone calls, llm). Read the matching topic BEFORE non-trivial work in that area — it is cheaper than a wrong call. Never bills; safe to call any time.
Nur Lesen
Idempotent
Eingabeschema
{'type': 'object', 'required': ['topic'], 'properties': {'topic': {'enum': ['setup', 'tools', 'media', 'gtm', 'research', 'data', 'compute'], 'type': 'string', 'description': 'Which reference to fetch.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'error': {'type': 'string', 'description': 'Set when the topic is unknown.'}, 'topic': {'type': 'string', 'description': 'The topic served.'}, 'topics': {'type': 'array', 'description': 'Valid topics, returned on an unknown-topic error.'}, 'content': {'type': 'string', 'description': 'The full reference document (markdown).'}}, 'additionalProperties': True}
llm
Ask Another LLM
Ask a DIFFERENT LLM a question and get its answer, billed per token from the Vaaya wallet (model cost + 3%, usually a fraction of a cent). Use it to get a second opinion from a rival model, cross-check an answer, summarize a huge blob cheaply, or query a specific model the user names (Kimi, GPT, Gemini, Claude, DeepSeek, and 300+ more). `model` accepts 'auto' (default: short prompts go cheap, long go mid), 'cheap' | 'mid' | 'best' tiers, or any exact OpenRouter slug like 'moonshotai/kimi-k3'. Typical costs: cheap tier well under 0.1 cents, best tier 1-3 cents per call. Not for the conversation you are already having — it is a one-shot ask to another model.
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['prompt'], 'properties': {'model': {'type': 'string', 'description': "'auto' (default), 'cheap', 'mid', 'best', or an exact OpenRouter model slug (e.g. 'moonshotai/kimi-k3', 'anthropic/claude-opus-5')."}, 'prompt': {'type': 'string', 'description': 'The question or task for the other model.'}, 'system': {'type': 'string', 'description': 'Optional system prompt for the other model.'}, 'max_tokens': {'type': 'number', 'description': 'Optional cap on the response length in tokens (default 4096, max 16384).'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'text': {'type': 'string', 'description': "The other model's answer."}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'model_used': {'type': 'string', 'description': 'The concrete model that served the request.'}, 'charged_usd': {'type': 'number', 'description': 'What the user pays for this call, in USD (model cost plus 3 percent).'}, 'prompt_tokens': {'type': 'number', 'description': 'Prompt tokens billed.'}, 'requested_model': {'type': 'string', 'description': "What the caller asked for ('auto', a tier, or a slug)."}, 'completion_tokens': {'type': 'number', 'description': 'Completion tokens billed.'}}, 'additionalProperties': True}
result
Poll an Async Job
Fetch the status + output of an async job started by `use` (e.g. a video render). Pass the `job_id` that `use` returned with `{ async: true }`. Returns `{ status, result?, progress?, charged_cents }`: `running` (still working — when the job reports it, `progress` carries `{ phase, percent, rendered_frames, total_frames, eta_sec }` and `hint` is a one-line summary like "rendering 42% (380/900 frames, ~120s left)", so you can tell real progress from a hang; wait a bit and call again), `succeeded` (`result` holds the output, e.g. the video URL; the call is charged now), or `failed`/`cancelled` (no charge; on `failed`, read `error` AND `hint` — `hint` carries the service's usage notes, which usually explain how to fix the call). Safe to call repeatedly — it never starts new work or double-charges. ALWAYS use this to retrieve an async result instead of re-running `use` (re-running starts a new paid job).
Nur Lesen
Externer Zugriff
Idempotent
Eingabeschema
{'type': 'object', 'required': ['job_id'], 'properties': {'job_id': {'type': 'string', 'description': 'The job_id returned by an async `use` call.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'hint': {'type': 'string', 'description': 'Human-readable progress summary.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'job_id': {'type': 'string', 'description': 'The polled job id.'}, 'result': {'description': 'Final output when succeeded.'}, 'status': {'enum': ['running', 'succeeded', 'failed', 'cancelled'], 'type': 'string', 'description': 'Job state.'}, 'progress': {'type': 'object', 'description': 'Progress detail (e.g. percent) while running.'}, 'charged_cents': {'type': 'number', 'description': 'Amount billed for this call, in cents.'}, 'balance_remaining_cents': {'type': 'number', 'description': 'Wallet balance remaining, in cents.'}}, 'additionalProperties': True}
session
Run Code in a Sandbox Session
Run a command or code in an open E2B sandbox session (started by `use` with action `create_session`, which returns a `session_id`). Pass `session_id` plus either `command` (a shell command) or `code` (+ optional `language`: python/javascript/bash). Returns stdout/stderr/exit_code (or the code result). The sandbox stays alive — and billed per second of uptime — until you `close` it; re-running reuses the SAME box, so filesystem + process state persist between calls. ALWAYS `close` when done.
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['session_id'], 'properties': {'code': {'type': 'string', 'description': 'Code to execute (alternative to `command`).'}, 'command': {'type': 'string', 'description': 'Shell command to run in the sandbox.'}, 'language': {'type': 'string', 'description': 'Language for `code`: python (default), javascript, or bash.'}, 'session_id': {'type': 'string', 'description': 'The session_id returned by create_session.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'result': {'description': 'Structured result, when the runtime returns one.'}, 'stderr': {'type': 'string', 'description': 'Captured standard error.'}, 'stdout': {'type': 'string', 'description': 'Captured standard output.'}, 'exit_code': {'type': 'number', 'description': 'Process exit code.'}}, 'additionalProperties': True}
stocks
Buy Tokenized Stocks
Buy tokenized stocks on Base using only the user’s prepaid Vaaya balance, never the welcome credit or the GitHub credit line. Commands: list (supported token tickers), portfolio (owned stocks and buying power), quote {symbol, amount_cents}, buy {symbol, amount_cents, idempotency_key}, order {order_id}. When the user asks to buy a specified stock and dollar amount, resolve its supported token ticker (Apple = AAPLc) and call buy directly; no activation or additional approval step. amount_cents is the maximum total prepaid spend including provider fees. Use a unique idempotency_key for each intended purchase and reuse it on retries. Query order until confirmed/failed; queued/submitted is not success. Do not increase the user’s spend or retry a failed purchase as a new order without instruction. Ask only for missing or ambiguous purchase details. If prepaid_required or buyingPowerCents is insufficient, offer a $15/$40/$80 prepaid pack: POST /api/v1/topup with pack_cents 1500/4000/8000 and the same account bearer token returns a Stripe Checkout url. With authorization for that pack amount, the user’s Instinct agent can pay the URL in its browser using the card saved in Instinct; otherwise give the URL to the user. Vaaya cannot charge Instinct’s card directly. Do not include card details or tokens in a handoff. Check GET /api/v1/wallet wallet.prepaid_cents, then portfolio buyingPowerCents before resuming the same purchase key. A share purchase alone does not authorize a top-up. Stop on needs_review as well as failed.
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['command'], 'properties': {'symbol': {'type': 'string', 'description': 'Token ticker from list, e.g. AAPLc. Required for quote and buy.'}, 'command': {'enum': ['list', 'portfolio', 'quote', 'buy', 'order'], 'type': 'string', 'description': 'list (supported tickers), portfolio (holdings + buying power), quote, buy, or order (status by id).'}, 'order_id': {'type': 'string', 'description': 'Order id returned by buy. Required for order.'}, 'amount_cents': {'type': 'integer', 'maximum': 1000000, 'minimum': 100, 'description': 'Maximum prepaid spend in cents, pool fees included. Required for quote and buy.'}, 'idempotency_key': {'type': 'string', 'maxLength': 128, 'minLength': 8, 'description': 'Unique per intended purchase; reuse it on retries. Required for buy.'}}, 'additionalProperties': False}
Ausgabeschema
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'quote/buy/order: quote id or order id.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'orders': {'type': 'array', 'description': 'portfolio: recent orders.'}, 'status': {'type': 'string', 'description': 'buy/order: queued | approving | ready | submitted | confirmed | failed | needs_review.'}, 'stocks': {'type': 'array', 'description': 'list: supported stocks with symbol, name, address, priceUsd and staleness.'}, 'symbol': {'type': 'string', 'description': 'Token ticker, e.g. AAPLc.'}, 'tokens': {'type': 'string', 'description': 'buy/order: tokens delivered once confirmed.'}, 'txHash': {'type': 'string', 'description': 'buy/order: Base transaction hash once broadcast.'}, 'address': {'type': 'string', 'description': 'portfolio: the user stock wallet on Base.'}, 'funding': {'type': 'string', 'description': 'list: always prepaid_only.'}, 'message': {'type': 'string', 'description': 'Human-readable failure detail.'}, 'holdings': {'type': 'array', 'description': 'portfolio: per-stock tokens, shares, valueUsd and staleness.'}, 'expiresAt': {'type': 'string', 'description': 'quote: ISO 8601 expiry (60s).'}, 'amountCents': {'type': 'number', 'description': 'Prepaid cents reserved for the purchase.'}, 'chargedCents': {'type': 'number', 'description': 'buy/order: cents actually charged once confirmed.'}, 'minimumTokens': {'type': 'string', 'description': 'quote: guaranteed minimum after 50 bps slippage.'}, 'totalValueUsd': {'type': 'string', 'description': 'portfolio: holdings value at the latest feed price.'}, 'estimatedTokens': {'type': 'string', 'description': 'quote: expected token amount.'}, 'buyingPowerCents': {'type': 'number', 'description': 'portfolio: prepaid cents available for stocks.'}}, 'additionalProperties': True}
use
Execute a Paid Service Call
Execute a single external call, and bill on success. Used for any external capability (image/video/audio generation, web search, scraping, email, document parsing, code sandbox, browser automation, embeddings, etc.). The server validates params against a registered schema and proxies to the upstream — you never pass URLs or API keys. Call it directly when you know the exact (service, action, params, max_cost_cents) — from the vaaya skill's catalog or a call you've made before; when unsure, get the call from `consult` rather than guessing.
Externer Zugriff
Eingabeschema
{'type': 'object', 'required': ['service', 'action', 'params', 'max_cost_cents'], 'properties': {'action': {'type': 'string', 'description': 'Action within the service (e.g. "search", "generate", "create_session"), taken from the call `consult` returned.'}, 'intent': {'type': 'string', 'description': "Optional: the one-line `why` from the consult call you're running (or the user's goal for it). Used only for internal transaction visibility — it never affects validation, billing, or execution. Pass it through when you have it."}, 'params': {'type': 'object', 'description': "Parameters from the call `consult` returned, validated against the service's registered schema.", 'additionalProperties': True}, 'service': {'type': 'string', 'description': 'Service identifier, taken verbatim from the call `consult` returned.'}, 'max_cost_cents': {'type': 'number', 'description': 'Hard ceiling in cents on what you will be charged. `use` refuses if the registry price exceeds this. Pick at least 2× the listed price so retries work.'}}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'data': {'description': 'Upstream result payload (URLs, text, ids, …).'}, 'async': {'type': 'boolean', 'description': 'True when the job runs asynchronously — poll with `result`.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'job_id': {'type': 'string', 'description': 'Async job id for `result` polling.'}, 'status': {'type': 'number', 'description': 'Upstream HTTP status when the call failed.'}, 'card_url': {'type': 'string', 'description': 'Only on `error: "card_required"`: a short-lived sign-in link where the user adds a card. Relay `data.message` to the user verbatim, then retry the same call once they have.'}, 'protocol': {'type': 'string', 'description': 'Settlement rail used (x402 / mpp / ledger).'}, 'charged_cents': {'type': 'number', 'description': 'Amount billed for this call, in cents.'}, 'transaction_id': {'type': 'string', 'description': 'Vaaya transaction id for this call.'}, 'balance_remaining_cents': {'type': 'number', 'description': 'Wallet balance remaining, in cents.'}}, 'additionalProperties': True}
vaaya_account
Show Connected Account & Balance
Show which Vaaya account this connection is linked to and its money state. Returns { email, name, user_id, connected_client, scopes, balance_cents, credit_line, available_cents, credits_url, switch_account }. Call it whenever the user asks "which account is connected", "what's my balance", "how much credit is left", or "how do I switch accounts" — and relay the answer. `credit_line` is the credit the account can spend past its prepaid balance (the welcome credit plus any GitHub-score line); `available_cents` = balance + active line, the number calls are gated on.
Nur Lesen
Idempotent
Eingabeschema
{'type': 'object', 'properties': {}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'name': {'type': 'string', 'description': 'Display name of the connected user.'}, 'email': {'type': 'string', 'description': 'Email of the connected Vaaya account.'}, 'scopes': {'type': 'array', 'description': 'Authorized scopes for this connection.'}, 'user_id': {'type': 'string', 'description': 'Vaaya user id.'}, 'needs_auth': {'type': 'boolean', 'description': 'True when this agent is not linked to a Vaaya user yet.'}, 'signup_uri': {'type': 'string', 'description': 'Where a new user signs up.'}, 'credits_url': {'type': 'string', 'description': 'Where the user buys credit packs.'}, 'instructions': {'type': 'string', 'description': 'What to tell the user to get connected.'}, 'balance_cents': {'type': 'number', 'description': 'Wallet balance remaining, in cents.'}, 'switch_account': {'type': 'string', 'description': 'How to connect a different account — relay to the user.'}, 'connected_client': {'type': 'string', 'description': 'OAuth client name this connection was made through.'}, 'verification_uri': {'type': 'string', 'description': 'Where the user approves the connection.'}, 'premium_allowance': {'type': 'object', 'description': 'Gated free-tier state for premium services: cap, purchased, spent, remaining (cents). Separate from wallet balance.'}}, 'additionalProperties': True}
vaaya_logout
Disconnect / Switch Vaaya Account
Disconnect this client from the current Vaaya account: revokes this connection's authorization server-side, so every later call fails with 401 until the user reconnects. Call it when the user asks to log out, sign out, disconnect, or switch Vaaya accounts — then relay the returned switch steps VERBATIM (the browser sign-out step is what actually enables switching accounts).
Destruktiv
Idempotent
Eingabeschema
{'type': 'object', 'properties': {}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the call succeeded.'}, 'error': {'type': 'string', 'description': 'Error code/message when ok=false.'}, 'message': {'type': 'string', 'description': 'What happened — relay to the user.'}, 'logged_out': {'type': 'boolean', 'description': 'True when the authorization was revoked.'}, 'to_switch_account': {'type': 'string', 'description': 'Exact steps to reconnect with a different account — relay verbatim.'}}, 'additionalProperties': True}
vaaya_onboard
Get Onboarding Instructions
Public onboarding hint for an agent whose user isn't linked to Vaaya yet. Returns where the human should go to connect (and sign up if new). Call this when vaaya_test_connection reports needs_auth, or any tool returns unauthorized, then relay the instructions to the user. If the user IS already linked it returns `first_call` instead — show `first_call.show_to_user` as written so they know what to try.
Nur Lesen
Idempotent
Eingabeschema
{'type': 'object', 'properties': {}}
Ausgabeschema
{'type': 'object', 'properties': {'message': {'type': 'string', 'description': 'Status message to relay to the user.'}, 'needs_auth': {'type': 'boolean', 'description': 'True when this agent is not linked to a Vaaya user yet.'}, 'signup_uri': {'type': 'string', 'description': 'Where a new user signs up.'}, 'instructions': {'type': 'string', 'description': 'What to tell the user to get connected.'}, 'already_linked': {'type': 'boolean', 'description': 'True when the agent is already connected.'}, 'verification_uri': {'type': 'string', 'description': 'Where the user approves the connection.'}}, 'additionalProperties': True}
vaaya_test_connection
Test Vaaya Connection
Round-trip ping that confirms the agent → Vaaya connection and whether the user is linked. Returns { ok:true, userId, scope, version, server_time, first_call } when linked — SHOW `first_call.show_to_user` to the user as written, it is the same set of starter examples the website and installer give them. Returns { ok:false, needs_auth:true, verification_uri, signup_uri, instructions } when not linked yet — relay that to the user so they can connect (and sign up if new).
Nur Lesen
Idempotent
Eingabeschema
{'type': 'object', 'properties': {}}
Ausgabeschema
{'type': 'object', 'properties': {'ok': {'type': 'boolean', 'description': 'True when the agent is linked to a Vaaya user.'}, 'scope': {'type': 'string', 'description': 'Space-separated authorized scopes.'}, 'userId': {'type': 'string', 'description': 'Linked Vaaya user id.'}, 'version': {'type': 'string', 'description': 'Server version.'}, 'needs_auth': {'type': 'boolean', 'description': 'True when this agent is not linked to a Vaaya user yet.'}, 'signup_uri': {'type': 'string', 'description': 'Where a new user signs up.'}, 'server_time': {'type': 'string', 'description': 'Server time, ISO 8601.'}, 'instructions': {'type': 'string', 'description': 'What to tell the user to get connected.'}, 'verification_uri': {'type': 'string', 'description': 'Where the user approves the connection.'}}, 'additionalProperties': True}
Verlauf
Letzte Tool-Änderungen
Geändert
stocks
1. October 2026 02:52
Geändert
buy
23. September 2026 02:51
Geändert
buy
21. September 2026 02:58
Geändert
vaaya_account
17. September 2026 12:56
Hinzugefügt
llm
17. September 2026 07:57
Hinzugefügt
close
17. September 2026 07:57
Hinzugefügt
session
17. September 2026 07:57
Hinzugefügt
buy
17. September 2026 07:57
Hinzugefügt
result
17. September 2026 07:57
Hinzugefügt
use
17. September 2026 07:57
Hinzugefügt
consult
17. September 2026 07:57
Hinzugefügt
docs
17. September 2026 07:57
Hinzugefügt
vaaya_logout
17. September 2026 07:57
Hinzugefügt
vaaya_account
17. September 2026 07:57
Hinzugefügt
vaaya_onboard
17. September 2026 07:57
Hinzugefügt
vaaya_test_connection
17. September 2026 07:57
Hinzugefügt
stocks
17. September 2026 07:57
Entdecken
Ähnliche MCP-Server
agentic-commerce
io.bosonprotocol/agentic-commerce
Enables on-chain commerce through Boson Protocol, including product offers, buyer and seller accounts, voucher exchanges, escrow-…
Wever Pay Open Exchange Public Beta
com.weverpay/public-testnet-alpha
Runs a Base Sepolia testnet exchange for agent participants, supporting wallets, USDC balances, signed offers, authorized purchas…
VIA Network: Agentic Commerce
xyz.getvia.app/via-network
Discovers products and sellers, supports negotiation and agent-mediated purchases, and settles eligible transactions in USDC on B…
FiatDock
com.fiatdock/fiatdock-mcp
Runs a USDC agent-services marketplace with Base blockchain intelligence, token safety and pricing, service calls, and fiat on-ra…
SCVD General Store
store.scvd/general-store
Offers x402 payment preflight and verification services alongside paid human tasks, signed records, memory anchors, observations,…
IMBA Agent Spend
com.imbawallet/agent
Manages USDT TRC-20 deposits and enables purchases of prepaid cards, eSIMs, gift cards, and crypto address screening.
Coal — Payments for AI agents
io.github.emmanuel39hanks/coal
Enables agents to discover merchants, pay for products or paywalls in USDC on Base, check balances, and retrieve purchased digita…
Nagora
shop.nagora/nagora
Supports searching listings, purchasing goods, tracking orders, and managing Nano-based escrow transactions.