Documentation
MCP tool reference

Start

OverviewQuickstartAuthenticationMaking callsDiscoveryMCPErrors & billingAPI schemaPay with x402

Guides

Web searchOneSearchOneFindOneScrapeResearchWeb scrapingGTM & leads

Data APIs

Public recordsReal estateSocial dataOn-chain & marketsCompliance & KYBOpen data

Execution APIs

BrowserLLMsMediaComputeFiles & storageEmailCommerce

vaaya / docs / reference

MCP tool reference

Find the right tool for a task, understand its inputs, and check the details before your agent makes a call.

MCP tools let your agent find services, run calls, and retrieve results through Vaaya. Connect your client, then use the guide below to understand what the agent can call.

Start with a task

ToolWhen to use it
consultDescribe what you want to do. Vaaya suggests the service, action, inputs, and maximum cost for the task.
useRun a service action with the inputs and spending limit you chose.
resultCheck an asynchronous job using the job ID returned by the call.

For example, ask your agent to find documentation for a library. It can use consult to choose a search service, then use to run the search. Check the current price before approving a paid call.

The inputs below come from the MCP server’s tool definitions. Availability depends on your account, client, and enabled features. Required inputs are marked in each table; some commands have additional requirements described in the schema. Expand the agent instructions for the full calling rules.

Read the text version for agents or use llms.txt for a shorter documentation index. For HTTP calls, see the API reference.

All tools (44)

stocks

View supported tokenized stocks, get a quote, buy with prepaid funds, and check your orders or holdings. Credit cannot fund a stock purchase.

Full instructions for agents

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 $10/$30/$100 prepaid pack: POST /api/v1/topup with pack_cents 1000/3000/10000 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.

InputRequired?TypeDescription
commandRequiredstringlist (supported tickers), portfolio (holdings + buying power), quote, buy, or order (status by id).
symbolOptionalstringToken ticker from list, e.g. AAPLc. Required for quote and buy.
amount_centsOptionalintegerMaximum prepaid spend in cents, pool fees included. Required for quote and buy.
idempotency_keyOptionalstringUnique per intended purchase; reuse it on retries. Required for buy.
order_idOptionalstringOrder id returned by buy. Required for order.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "command": {
      "type": "string",
      "enum": [
        "list",
        "portfolio",
        "quote",
        "buy",
        "order"
      ],
      "description": "list (supported tickers), portfolio (holdings + buying power), quote, buy, or order (status by id)."
    },
    "symbol": {
      "type": "string",
      "description": "Token ticker from list, e.g. AAPLc. Required for quote and buy."
    },
    "amount_cents": {
      "type": "integer",
      "minimum": 100,
      "maximum": 1000000,
      "description": "Maximum prepaid spend in cents, pool fees included. Required for quote and buy."
    },
    "idempotency_key": {
      "type": "string",
      "minLength": 8,
      "maxLength": 128,
      "description": "Unique per intended purchase; reuse it on retries. Required for buy."
    },
    "order_id": {
      "type": "string",
      "description": "Order id returned by buy. Required for order."
    }
  },
  "required": [
    "command"
  ],
  "additionalProperties": false
}

vaaya_test_connection

Check that your agent is connected to Vaaya and find out whether you need to sign in.

Full instructions for agents

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).

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

vaaya_onboard

Get the sign-in instructions for connecting an agent to your Vaaya account.

Full instructions for agents

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.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

vaaya_account

See the connected account, its balance, and its available credit.

Full instructions for agents

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 card-backed credit the account can spend past its prepaid balance (a $2 welcome line plus any GitHub-score line); `available_cents` = balance + active line, the number calls are gated on.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

vaaya_logout

Disconnect the current Vaaya session.

Full instructions for agents

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).

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

docs

Read Vaaya documentation for a topic.

Full instructions for agents

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.

InputRequired?TypeDescription
topicRequiredstringWhich reference to fetch.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "enum": [
        "setup",
        "tools",
        "media",
        "gtm",
        "research",
        "data",
        "compute"
      ],
      "description": "Which reference to fetch."
    }
  },
  "required": [
    "topic"
  ]
}

consult

Describe your task to get suggested service calls or a question about missing details. This tool does not run the suggested calls.

Full instructions for agents

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.

InputRequired?TypeDescription
intentRequiredstringPlain-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.
Full input schema (JSON)
{
  "type": "object",
  "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."
    }
  },
  "required": [
    "intent"
  ]
}

use

Run one service action with its inputs and a maximum cost. Successful calls are charged to your account.

Full instructions for agents

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.

InputRequired?TypeDescription
serviceRequiredstringService identifier, taken verbatim from the call consult returned.
actionRequiredstringAction within the service (e.g. "search", "generate", "create_session"), taken from the call consult returned.
paramsRequiredobjectParameters from the call consult returned, validated against the service's registered schema.
max_cost_centsRequirednumberHard 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.
intentOptionalstringOptional: 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.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "service": {
      "type": "string",
      "description": "Service identifier, taken verbatim from the call `consult` returned."
    },
    "action": {
      "type": "string",
      "description": "Action within the service (e.g. \"search\", \"generate\", \"create_session\"), taken from the call `consult` returned."
    },
    "params": {
      "type": "object",
      "description": "Parameters from the call `consult` returned, validated against the service's registered schema.",
      "additionalProperties": true
    },
    "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."
    },
    "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."
    }
  },
  "required": [
    "service",
    "action",
    "params",
    "max_cost_cents"
  ]
}

result

Check the progress and output of a job started by use. Poll the existing job instead of starting another paid call.

Full instructions for agents

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).

InputRequired?TypeDescription
job_idRequiredstringThe job_id returned by an async use call.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "description": "The job_id returned by an async `use` call."
    }
  },
  "required": [
    "job_id"
  ]
}

buy

Make an authorized purchase using your own card. Purchases through this tool do not use your Vaaya balance. Read the purchase and approval requirements below.

Full instructions for agents

Buy something for the USER — a physical good, a ticket, a subscription — paid by the user's OWN card, never from their Vaaya balance. First use `setup` to check the Link wallet and shipping address; resolve missing setup once. Prefer guest checkout; when login is required, let the user sign in or sign up in the checkout browser. 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 a merchant login is needed, prefer direct browser sign-in; only if the user chooses to save credentials, call `credentials` { merchant, username, password } (stored encrypted, never shown again) then `checkout` again. 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. Resume other pauses with 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.

InputRequired?TypeDescription
commandRequiredstringWhat to do. purchase is the one-call seamless path.
queryOptionalstringWhat to look for (search).
itemOptionalstringWhat exactly is being bought, in the user's words — variant, size, quantity (purchase, propose).
merchantOptionalstringMerchant host or URL, e.g. bombas.com (purchase, propose, credentials).
total_centsOptionalnumberThe full total the user will pay, in cents (purchase, propose).
currencyOptionalstringISO currency, default 'usd'.
urlOptionalstringThe exact product page the item came from — the driver starts there (purchase, propose).
notesOptionalstringOne line for the driver/user: variant, size, colour, quantity, delivery window.
confirmedOptionalbooleantrue when the user has said yes to this exact item and total in the conversation (purchase, propose).
confirmationOptionalstringThe user's own words approving it, verbatim (purchase, propose).
approval_idOptionalstringThe approval returned by purchase/propose (status, checkout).
paramsOptionalobjectThe merchant's own purchase body (product id, quantity, email, shipping) for a protocol merchant (purchase, checkout).
nameOptionalstringFull name for shipping (address).
line1OptionalstringStreet address (address).
line2OptionalstringApartment / unit (address).
cityOptionalstringCity (address).
stateOptionalstringState / region (address).
postal_codeOptionalstringPostal / ZIP code (address).
countryOptionalstringTwo-letter country code, e.g. US (address).
phoneOptionalstringContact phone for delivery (address).
emailOptionalstringContact email for the order; defaults to the account email (address).
usernameOptionalstringEmail/username at the merchant (credentials).
passwordOptionalstringPassword at the merchant — stored encrypted, never returned (credentials).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "command": {
      "type": "string",
      "enum": [
        "setup",
        "search",
        "purchase",
        "propose",
        "status",
        "checkout",
        "reconcile",
        "address",
        "credentials"
      ],
      "description": "What to do. `purchase` is the one-call seamless path."
    },
    "query": {
      "type": "string",
      "description": "What to look for (`search`)."
    },
    "item": {
      "type": "string",
      "description": "What exactly is being bought, in the user's words — variant, size, quantity (`purchase`, `propose`)."
    },
    "merchant": {
      "type": "string",
      "description": "Merchant host or URL, e.g. bombas.com (`purchase`, `propose`, `credentials`)."
    },
    "total_cents": {
      "type": "number",
      "description": "The full total the user will pay, in cents (`purchase`, `propose`)."
    },
    "currency": {
      "type": "string",
      "description": "ISO currency, default 'usd'."
    },
    "url": {
      "type": "string",
      "description": "The exact product page the item came from — the driver starts there (`purchase`, `propose`)."
    },
    "notes": {
      "type": "string",
      "description": "One line for the driver/user: variant, size, colour, quantity, delivery window."
    },
    "confirmed": {
      "type": "boolean",
      "description": "true when the user has said yes to this exact item and total in the conversation (`purchase`, `propose`)."
    },
    "confirmation": {
      "type": "string",
      "description": "The user's own words approving it, verbatim (`purchase`, `propose`)."
    },
    "approval_id": {
      "type": "string",
      "description": "The approval returned by purchase/propose (`status`, `checkout`)."
    },
    "params": {
      "type": "object",
      "description": "The merchant's own purchase body (product id, quantity, email, shipping) for a protocol merchant (`purchase`, `checkout`).",
      "additionalProperties": true
    },
    "name": {
      "type": "string",
      "description": "Full name for shipping (`address`)."
    },
    "line1": {
      "type": "string",
      "description": "Street address (`address`)."
    },
    "line2": {
      "type": "string",
      "description": "Apartment / unit (`address`)."
    },
    "city": {
      "type": "string",
      "description": "City (`address`)."
    },
    "state": {
      "type": "string",
      "description": "State / region (`address`)."
    },
    "postal_code": {
      "type": "string",
      "description": "Postal / ZIP code (`address`)."
    },
    "country": {
      "type": "string",
      "description": "Two-letter country code, e.g. US (`address`)."
    },
    "phone": {
      "type": "string",
      "description": "Contact phone for delivery (`address`)."
    },
    "email": {
      "type": "string",
      "description": "Contact email for the order; defaults to the account email (`address`)."
    },
    "username": {
      "type": "string",
      "description": "Email/username at the merchant (`credentials`)."
    },
    "password": {
      "type": "string",
      "description": "Password at the merchant — stored encrypted, never returned (`credentials`)."
    }
  },
  "required": [
    "command"
  ]
}

session

Run a command or code in an existing E2B sandbox. Files and processes remain available between calls. Close the session when finished to stop billing.

Full instructions for agents

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.

InputRequired?TypeDescription
session_idRequiredstringThe session_id returned by create_session.
commandOptionalstringShell command to run in the sandbox.
codeOptionalstringCode to execute (alternative to command).
languageOptionalstringLanguage for code: python (default), javascript, or bash.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "session_id": {
      "type": "string",
      "description": "The session_id returned by create_session."
    },
    "command": {
      "type": "string",
      "description": "Shell command to run in the sandbox."
    },
    "code": {
      "type": "string",
      "description": "Code to execute (alternative to `command`)."
    },
    "language": {
      "type": "string",
      "description": "Language for `code`: python (default), javascript, or bash."
    }
  },
  "required": [
    "session_id"
  ]
}

close

Close an E2B sandbox session and stop its usage charges.

Full instructions for agents

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).

InputRequired?TypeDescription
session_idRequiredstringThe session_id to close.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "session_id": {
      "type": "string",
      "description": "The session_id to close."
    }
  },
  "required": [
    "session_id"
  ]
}

llm

Send a prompt to another language model and return its answer.

Full instructions for agents

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.

InputRequired?TypeDescription
promptRequiredstringThe question or task for the other model.
modelOptionalstring'auto' (default), 'cheap', 'mid', 'best', or an exact OpenRouter model slug (e.g. 'moonshotai/kimi-k3', 'anthropic/claude-opus-5').
systemOptionalstringOptional system prompt for the other model.
max_tokensOptionalnumberOptional cap on the response length in tokens (default 4096, max 16384).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "prompt": {
      "type": "string",
      "description": "The question or task for the other model."
    },
    "model": {
      "type": "string",
      "description": "'auto' (default), 'cheap', 'mid', 'best', or an exact OpenRouter model slug (e.g. 'moonshotai/kimi-k3', 'anthropic/claude-opus-5')."
    },
    "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)."
    }
  },
  "required": [
    "prompt"
  ]
}

gtm_brain

Read and manage the company knowledge your outreach tools use.

Full instructions for agents

Read or update the user's GTM brain — the campaign-free source of truth for who they're reaching and what they're selling. action='get' returns identity/value-prop, the default ICP/audience, pain/proof/voice/guardrails, the active intent, and the lead count. action='set_intent' declares what the user is DOING — kind ('sell'|'recruit'|'fundraise'|'job_hunt'|'custom'), market, angle, goal — which grounds messaging later; this is campaign-free (no outreach happens). action='get_intent' returns the active intent; action='list_intents' returns intent history.

InputRequired?TypeDescription
actionOptionalstringWhat to do. Defaults to 'get'.
kindOptionalstringset_intent: what the user is doing. Defaults to 'sell'.
marketOptionalstringset_intent: the target market/audience in plain English.
angleOptionalstringset_intent: the core positioning/angle for this outreach.
goalOptionalstringset_intent: the outcome the user wants.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "get",
        "set_intent",
        "get_intent",
        "list_intents"
      ],
      "description": "What to do. Defaults to 'get'."
    },
    "kind": {
      "type": "string",
      "enum": [
        "sell",
        "recruit",
        "fundraise",
        "job_hunt",
        "custom"
      ],
      "description": "set_intent: what the user is doing. Defaults to 'sell'."
    },
    "market": {
      "type": "string",
      "description": "set_intent: the target market/audience in plain English."
    },
    "angle": {
      "type": "string",
      "description": "set_intent: the core positioning/angle for this outreach."
    },
    "goal": {
      "type": "string",
      "description": "set_intent: the outcome the user wants."
    }
  }
}

gtm_leads

Manage your saved leads.

Full instructions for agents

Manage the user's campaign-free lead repository (people to reach out to — prospects, candidates, targets, investors; differently tagged for different uses). action='add' upserts people you already have (paste a list); each person = { first_name, last_name, title, company, email, linkedin_url, why_prioritized?, hook?, source? }; deduped per person within the user's scope so re-adding updates, never duplicates. action='list' returns leads (optional `q` search, `tag_id`/`segment_id` membership filter, `limit`). action='get' returns one lead by `id`, with its tags and any inbound reply conversations linked to them. action='tag' applies labels: { id | ids:[…], tags:["founder","warm-intro"] } (bulk-capable; creates missing tags, idempotent). action='untag' removes a label: { id | ids:[…], tag_id }. To DISCOVER new people via paid search, use `gtm_leads_find`; to group leads, use `gtm_segments`.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
peopleOptionalarrayadd: the people to upsert.
qOptionalstringlist: free-text filter.
tag_idOptionalstringlist: only leads with this tag.
segment_idOptionalstringlist: only leads in this segment.
limitOptionalnumberlist: max rows (default 200, max 1000).
idOptionalstringget/tag/untag: the lead id.
idsOptionalarraytag/untag: MANY lead ids at once (bulk; use instead of id).
tagsOptionalarraytag: label names to apply.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "add",
        "list",
        "get",
        "tag",
        "untag"
      ],
      "description": "Defaults to 'list'."
    },
    "people": {
      "type": "array",
      "description": "add: the people to upsert.",
      "items": {
        "type": "object",
        "properties": {
          "first_name": {
            "type": "string",
            "description": "Person's first name."
          },
          "last_name": {
            "type": "string",
            "description": "Person's last name."
          },
          "title": {
            "type": "string",
            "description": "Job title, e.g. \"Head of RevOps\"."
          },
          "company": {
            "type": "string",
            "description": "Company the person works at."
          },
          "email": {
            "type": "string",
            "description": "Email address, if known."
          },
          "linkedin_url": {
            "type": "string",
            "description": "LinkedIn profile URL, if known."
          },
          "why_prioritized": {
            "type": "string",
            "description": "Why this person is worth reaching out to now."
          },
          "hook": {
            "type": "string",
            "description": "Personalization hook to open outreach with."
          },
          "source": {
            "type": "string",
            "description": "Where this lead came from (e.g. \"conference list\", \"referral\")."
          }
        }
      }
    },
    "q": {
      "type": "string",
      "description": "list: free-text filter."
    },
    "tag_id": {
      "type": "string",
      "description": "list: only leads with this tag."
    },
    "segment_id": {
      "type": "string",
      "description": "list: only leads in this segment."
    },
    "limit": {
      "type": "number",
      "description": "list: max rows (default 200, max 1000)."
    },
    "id": {
      "type": "string",
      "description": "get/tag/untag: the lead id."
    },
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "tag/untag: MANY lead ids at once (bulk; use instead of `id`)."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "tag: label names to apply."
    }
  }
}

gtm_leads_find

Find people or companies that match your prospect criteria.

Full instructions for agents

DISCOVER new ICP-fit people via paid Exa search and add them to the campaign-free lead repository (NOT a campaign). Bills per search. Pass `job_titles` (required — one search per title, up to 5) plus optional `seniority`, `industries`, `headcount`, `person_locations`, `company_locations`, and `max_fetch` (default 25). Returns { found, added, charged_cents }. The added people land in `gtm_leads` for review.

InputRequired?TypeDescription
job_titlesRequiredarrayICP job titles (required).
seniorityOptionalarraySeniority filters, e.g. ["vp", "director", "c_suite"].
industriesOptionalarrayIndustry filters, e.g. ["saas", "fintech"].
headcountOptionalarrayCompany size ranges, e.g. ["11-50", "51-200"].
person_locationsOptionalarrayWhere the person is located, e.g. ["san francisco", "united kingdom"].
company_locationsOptionalarrayWhere the company is headquartered.
max_fetchOptionalnumberMax people to fetch (default 25).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "job_titles": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "ICP job titles (required)."
    },
    "seniority": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Seniority filters, e.g. [\"vp\", \"director\", \"c_suite\"]."
    },
    "industries": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Industry filters, e.g. [\"saas\", \"fintech\"]."
    },
    "headcount": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Company size ranges, e.g. [\"11-50\", \"51-200\"]."
    },
    "person_locations": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Where the person is located, e.g. [\"san francisco\", \"united kingdom\"]."
    },
    "company_locations": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Where the company is headquartered."
    },
    "max_fetch": {
      "type": "number",
      "description": "Max people to fetch (default 25)."
    }
  },
  "required": [
    "job_titles"
  ]
}

gtm_segments

Organize leads into segments for your outreach.

Full instructions for agents

Group campaign-free leads into OPTIONAL segments — each carries its own messaging angle/goal (and, later, a schedule). The same lead can sit in many segments with no duplication. action='define' creates-or-updates a segment by name: { name, angle?, goal?, intent_id?, channel? }. `channel` is the segment's HARD channel setting — once set, EVERY draft for the segment uses it (the UI shows it on the segment page under Positioning): 'email' | 'mixed' to clear it. (LinkedIn channels were retired 2026-09 — there is no LinkedIn wire; email is the only channel that sends.) action='add_leads' links leads: { segment_id, lead_ids:[...] } (idempotent). action='remove_lead': { segment_id, lead_id }. action='list' returns segments with member counts. action='get': { id }. action='coverage': { segment_id } returns readiness buckets (members / drafted / approved / sent / with assets). Segments are NOT campaigns and never send anything by themselves — an explicit gtm_automation message_auto_send rule (opt-in) is the only way a segment's APPROVED messages go out automatically.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
nameOptionalstringdefine: the segment name.
angleOptionalstringdefine: the per-segment messaging angle.
goalOptionalstringdefine: the segment goal.
intent_idOptionalstringdefine: optional linked intent id.
channelOptionalstringdefine: the segment's hard channel — 'mixed' clears it. Omit to leave unchanged.
segment_idOptionalstringadd_leads/remove_lead/coverage: the segment id.
idOptionalstringget: the segment id.
lead_idsOptionalarrayadd_leads: lead ids to link.
lead_idOptionalstringremove_lead: the lead id to unlink.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "define",
        "list",
        "get",
        "add_leads",
        "remove_lead",
        "coverage"
      ],
      "description": "Defaults to 'list'."
    },
    "name": {
      "type": "string",
      "description": "define: the segment name."
    },
    "angle": {
      "type": "string",
      "description": "define: the per-segment messaging angle."
    },
    "goal": {
      "type": "string",
      "description": "define: the segment goal."
    },
    "intent_id": {
      "type": "string",
      "description": "define: optional linked intent id."
    },
    "channel": {
      "type": "string",
      "enum": [
        "email",
        "mixed"
      ],
      "description": "define: the segment's hard channel — 'mixed' clears it. Omit to leave unchanged."
    },
    "segment_id": {
      "type": "string",
      "description": "add_leads/remove_lead/coverage: the segment id."
    },
    "id": {
      "type": "string",
      "description": "get: the segment id."
    },
    "lead_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "add_leads: lead ids to link."
    },
    "lead_id": {
      "type": "string",
      "description": "remove_lead: the lead id to unlink."
    }
  }
}

gtm_message

Work with outreach messages for your leads.

Full instructions for agents

Draft, store, version and approve outbound messages in the reusable message bank — MANUAL-FIRST: this tool NEVER sends. action='draft' generates a personalized message for a lead, grounded in the brain (voice/pain/proof/guardrails) + the active intent + an optional segment angle: { lead_id, segment_id?, channel } where channel = email (the only channel that sends; LinkedIn channels were retired 2026-09 — older linkedin_* drafts still render and are copy-and-paste only). If the segment has a channel SET (its hard setting), drafting uses THAT channel regardless of the one passed. Stored as a new draft version. action='store' saves your own copy: { lead_id?, segment_id?, channel?, subject?, body }. action='edit' creates a NEW version (history preserved): { id, body, subject? }. action='approve': { id }. action='list' returns every version for a lead: { lead_id }. action='get': { id }. action='mark_sent' RECORDS that the human sent it (no provider call): { id, via? }. To actually send, the user sends manually from their own account.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
lead_idOptionalstringdraft/store/list: the lead.
segment_idOptionalstringdraft/store: optional segment for the angle.
channelOptionalstringdraft/store: defaults to 'email'.
subjectOptionalstringstore/edit: email subject line.
bodyOptionalstringstore/edit: the message body.
idOptionalstringget/approve/edit/mark_sent: the message id.
viaOptionalstringmark_sent: how it was sent (e.g. "gmail", "linkedin").
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "draft",
        "store",
        "get",
        "list",
        "approve",
        "edit",
        "mark_sent"
      ],
      "description": "Defaults to 'list'."
    },
    "lead_id": {
      "type": "string",
      "description": "draft/store/list: the lead."
    },
    "segment_id": {
      "type": "string",
      "description": "draft/store: optional segment for the angle."
    },
    "channel": {
      "type": "string",
      "enum": [
        "email"
      ],
      "description": "draft/store: defaults to 'email'."
    },
    "subject": {
      "type": "string",
      "description": "store/edit: email subject line."
    },
    "body": {
      "type": "string",
      "description": "store/edit: the message body."
    },
    "id": {
      "type": "string",
      "description": "get/approve/edit/mark_sent: the message id."
    },
    "via": {
      "type": "string",
      "description": "mark_sent: how it was sent (e.g. \"gmail\", \"linkedin\")."
    }
  }
}

gtm_asset

Manage assets used in your outreach.

Full instructions for agents

Attach, list and detach per-lead multimodal assets (a personalized research PDF, intro video, voice note, one-pager) — stored durably and retrievable per lead, reusable across segments. action='attach' links an artifact you already produced to a lead: { lead_id, artifact_id, role } where role ∈ research_pdf|intro_video|voice_note|one_pager|image|other (you can only attach your own artifacts). action='list' returns a lead's assets with presigned URLs (in-flight renders show as 'pending'): { lead_id }. action='detach': { lead_id, asset_id }. To GENERATE a new asset (paid), use `gtm_asset_produce`.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
lead_idOptionalstringthe lead.
artifact_idOptionalstringattach: the vaaya artifact id.
roleOptionalstringattach: the asset role. Defaults to 'other'.
asset_idOptionalstringdetach: the lead_asset id.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "attach",
        "list",
        "detach"
      ],
      "description": "Defaults to 'list'."
    },
    "lead_id": {
      "type": "string",
      "description": "the lead."
    },
    "artifact_id": {
      "type": "string",
      "description": "attach: the vaaya artifact id."
    },
    "role": {
      "type": "string",
      "enum": [
        "research_pdf",
        "intro_video",
        "voice_note",
        "one_pager",
        "image",
        "other"
      ],
      "description": "attach: the asset role. Defaults to 'other'."
    },
    "asset_id": {
      "type": "string",
      "description": "detach: the lead_asset id."
    }
  }
}

gtm_asset_produce

Produce an asset for an outreach task.

Full instructions for agents

Produce a per-lead asset via a paid vendor call (e.g. a personalized intro video, voice note, image), then attach it to the lead. First `consult` to get the exact { service, action, params } for the media you want; pass them here plus `lead_id` and `role`. Bills through the wallet like any `use` call. Async renders (video) return { async:true, job_id } and the asset shows as 'pending' until the render lands (it reconciles automatically); sync renders attach immediately.

InputRequired?TypeDescription
lead_idRequiredstringthe lead to attach to.
serviceRequiredstringthe vendor service (from consult), e.g. "fal".
actionRequiredstringthe vendor action (from consult).
paramsOptionalobjectthe vendor params (from consult).
roleOptionalstringthe asset role. Defaults to 'other'.
max_cost_centsOptionalnumberspend cap for this produce.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "lead_id": {
      "type": "string",
      "description": "the lead to attach to."
    },
    "service": {
      "type": "string",
      "description": "the vendor service (from consult), e.g. \"fal\"."
    },
    "action": {
      "type": "string",
      "description": "the vendor action (from consult)."
    },
    "params": {
      "type": "object",
      "description": "the vendor params (from consult)."
    },
    "role": {
      "type": "string",
      "enum": [
        "research_pdf",
        "intro_video",
        "voice_note",
        "one_pager",
        "image",
        "other"
      ],
      "description": "the asset role. Defaults to 'other'."
    },
    "max_cost_cents": {
      "type": "number",
      "description": "spend cap for this produce."
    }
  },
  "required": [
    "lead_id",
    "service",
    "action"
  ]
}

gtm_lead_enrich

Add information to a lead record.

Full instructions for agents

Reveal a lead's contact info and write it onto the lead — a three-rung ladder, each rung only when the cap covers it: ContactOut (work email by linkedin_url, 10¢, free on a miss) → Nyne (55¢ — full profile with emails AND phone from any identifier) → Apollo (10¢ final backup). Pass { lead_id, max_cost_cents: 70 } for the full ladder. Bills through the wallet. Returns { ok, email, phone?, charged_cents }. For a reverse lookup on someone who is NOT a lead yet (a bare email / phone number / social handle), call use({service:'nyne', action:'person-enrich'}) directly and poll nyne:result.

InputRequired?TypeDescription
lead_idRequiredstringthe lead to enrich.
max_cost_centsOptionalnumberspend cap (default 10 = ContactOut only; 70 runs the full ContactOut→Nyne→Apollo ladder).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "lead_id": {
      "type": "string",
      "description": "the lead to enrich."
    },
    "max_cost_cents": {
      "type": "number",
      "description": "spend cap (default 10 = ContactOut only; 70 runs the full ContactOut→Nyne→Apollo ladder)."
    }
  },
  "required": [
    "lead_id"
  ]
}

gtm_recall

Retrieve saved context for your outreach work.

Full instructions for agents

Ask the GTM brain what it knows. Fuses semantically-recalled facts (chosen messaging angles, sent messages, enriched leads — everything the brain has learned) with matching leads and segments. Use it to ground your next move: 'what do we know about X', 'who in fintech haven't I contacted', 'which segments cover founders'. Pass { query }. Returns { facts, leads, segments }.

InputRequired?TypeDescription
queryRequiredstringwhat you want to recall.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "what you want to recall."
    }
  },
  "required": [
    "query"
  ]
}

gtm_job

Check and manage background outreach jobs.

Full instructions for agents

Program the GTM scheduler — durable, multi-step jobs that run on a thin server tick even when no agent is connected (multi-day workflows, standing watches, refreshes). action='schedule' creates one: { name, steps:[...], max_cost_cents?, related_segment_id?, related_lead_id?, start_at? }. Each step is either { type:'service', service, action, params, max_price_cents? } (a paid/free dispatcher call — poll signals, enrich, find) or { type:'reasoning', goal } (a bounded brain-grounded generation that records a decision). Steps run in order; a failed step or the budget cap PAUSES the job. Jobs NEVER send — manual-first holds. action='list' / 'get' { id } / 'cancel' { id }.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
nameOptionalstringschedule: a human label.
stepsOptionalarrayschedule: the ordered steps.
max_cost_centsOptionalnumberschedule: total spend cap for the job (default 300).
related_segment_idOptionalstringschedule: link the job to a segment (optional).
related_lead_idOptionalstringschedule: link the job to a lead (optional).
idOptionalstringget/cancel: the job id.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "schedule",
        "list",
        "get",
        "cancel"
      ],
      "description": "Defaults to 'list'."
    },
    "name": {
      "type": "string",
      "description": "schedule: a human label."
    },
    "steps": {
      "type": "array",
      "description": "schedule: the ordered steps.",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "service",
              "reasoning"
            ],
            "description": "'service' runs a paid call; 'reasoning' is an LLM step over prior results."
          },
          "service": {
            "type": "string",
            "description": "service step: service identifier (from consult)."
          },
          "action": {
            "type": "string",
            "description": "service step: action within the service."
          },
          "params": {
            "type": "object",
            "description": "service step: params for the call."
          },
          "goal": {
            "type": "string",
            "description": "reasoning step: what to derive from prior steps."
          },
          "max_price_cents": {
            "type": "number",
            "description": "service step: per-step spend cap in cents."
          }
        },
        "required": [
          "type"
        ]
      }
    },
    "max_cost_cents": {
      "type": "number",
      "description": "schedule: total spend cap for the job (default 300)."
    },
    "related_segment_id": {
      "type": "string",
      "description": "schedule: link the job to a segment (optional)."
    },
    "related_lead_id": {
      "type": "string",
      "description": "schedule: link the job to a lead (optional)."
    },
    "id": {
      "type": "string",
      "description": "get/cancel: the job id."
    }
  }
}

gtm_composio

Use connected applications for outreach tasks.

Full instructions for agents

Act on the user's OWN connected calendar / CRM / spreadsheet (via Composio hosted auth). Pass `action`: 'book' (create a calendar event, 1¢), 'crm_log' (write a HubSpot note, free), or 'sheet_push' (update a Google Sheet, free) + `params` { arguments: <the tool's input>, tool_slug?: <override the default tool> }. If the account isn't connected it returns `not_connected` with a `connect_url` to send the user. Defaults: book→GOOGLECALENDAR_CREATE_EVENT, crm_log→HUBSPOT_CREATE_NOTE, sheet_push→GOOGLESHEETS_BATCH_UPDATE.

InputRequired?TypeDescription
actionRequiredstringWhich capability to invoke.
paramsOptionalobjectComposio tool input: { arguments, tool_slug? }.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "book",
        "crm_log",
        "sheet_push"
      ],
      "description": "Which capability to invoke."
    },
    "params": {
      "type": "object",
      "description": "Composio tool input: { arguments, tool_slug? }.",
      "additionalProperties": true
    }
  },
  "required": [
    "action"
  ]
}

gtm_signal_create

Set up a signal to look for events relevant to your prospects.

Full instructions for agents

Create a standing SIGNAL WATCH: a plain-English ICP query Vaaya polls (~every 6h via Exa) for fresh buying signals — funding, hiring, launches, leadership changes, press. e.g. 'HVAC companies founded in Los Angeles' or 'seed-stage B2B SaaS that just raised'. Pass `query` (required) and optional `signal_types` (subset of funding|hiring|launch|leadership|press; default all). This is a thin alias of `worker_create` with kind:'signal' — the watch is a 'signal worker' and appears on the Workers dashboard (the one watching surface), where each company can be worked into outreach by hand. Returns { ok }. Creating a watch is free; polling spends from the user's balance under the workers daily budget.

InputRequired?TypeDescription
queryRequiredstringPlain-English ICP / what to watch for.
signal_typesOptionalarrayWhich buying-signal types to watch for (default: all).
sentimentOptionalarrayKeep only news with these sentiments (default: all).
high_signal_onlyOptionalbooleanKeep only high-relevance news articles (fewer, stronger findings).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Plain-English ICP / what to watch for."
    },
    "signal_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "funding",
          "hiring",
          "launch",
          "leadership",
          "press"
        ]
      },
      "description": "Which buying-signal types to watch for (default: all)."
    },
    "sentiment": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "positive",
          "negative",
          "neutral"
        ]
      },
      "description": "Keep only news with these sentiments (default: all)."
    },
    "high_signal_only": {
      "type": "boolean",
      "description": "Keep only high-relevance news articles (fewer, stronger findings)."
    }
  },
  "required": [
    "query"
  ]
}

gtm_signal_act

Act on a signal found for a prospect.

Full instructions for agents

Act on a signal finding — the exit from discovery into the lead repository (VAA-100). action='find_people' (default) runs a paid Exa search (≤5¢) for decision-makers at the finding's company and upserts them into `gtm_leads` with source 'signal' and the signal headline as their hook/why; action='dismiss' marks the finding handled without spending. Both stamp acted_at so a finding is handled once (a second find_people returns already_acted). Pass `finding_id` (from `worker_findings` or the Workers page's buying-signals feed) and optionally `roles` to steer who to look for (default founder/CEO/CTO/Head-of/VP). Returns { ok, action, found, added, charged_cents }.

InputRequired?TypeDescription
finding_idRequiredstringThe worker finding to act on.
actionOptionalstring'find_people' (default) finds decision-makers at the company; 'dismiss' marks handled without spending.
rolesOptionalarrayfind_people: roles to look for at the company.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "finding_id": {
      "type": "string",
      "description": "The worker finding to act on."
    },
    "action": {
      "type": "string",
      "enum": [
        "find_people",
        "dismiss"
      ],
      "description": "'find_people' (default) finds decision-makers at the company; 'dismiss' marks handled without spending."
    },
    "roles": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "find_people: roles to look for at the company."
    }
  },
  "required": [
    "finding_id"
  ]
}

gtm_automation

Manage recurring outreach work and its rules.

Full instructions for agents

Manage the user's OPT-IN autopilot rules (VAA-105). With NO rules, nothing ever auto-sends — creating a rule is the user explicitly turning automation on for a flow they know works, so only do it when they clearly ask. Kinds: 'reply_auto_send' (a classified inbound reply matching `intent_classes` at ≥ `min_confidence` — default 0.8 — is approved + sent instead of held in the inbox) and 'message_auto_send' (an APPROVED email for a member of `segment_id` sends automatically on approval; `channel` is always 'email' — the LinkedIn wire was retired 2026-09). Every rule has a `daily_cap` (default 10); the send paths' gates (throttle, wallet, GTM_ENABLED) still apply, sends bill the user like manual ones, and each auto-send is logged to the brain. action='create'|'list'|'pause'|'resume'|'delete' (pause/resume/delete take `rule_id`).

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
kindOptionalstringcreate: 'reply_auto_send' auto-sends matching classified inbound replies; 'message_auto_send' auto-sends approved segment messages.
intent_classesOptionalarrayreply rules: which intents may auto-send (e.g. interested, meeting_request).
min_confidenceOptionalnumberreply rules: classifier floor (default 0.8).
segment_idOptionalstringmessage rules: only members of this segment.
channelOptionalstringmessage rules: which channel auto-sends (only 'email').
daily_capOptionalnumberMax auto-sends per day (default 10).
rule_idOptionalstringpause/resume/delete: the rule.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "create",
        "list",
        "pause",
        "resume",
        "delete"
      ],
      "description": "Defaults to 'list'."
    },
    "kind": {
      "type": "string",
      "enum": [
        "reply_auto_send",
        "message_auto_send"
      ],
      "description": "create: 'reply_auto_send' auto-sends matching classified inbound replies; 'message_auto_send' auto-sends approved segment messages."
    },
    "intent_classes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "reply rules: which intents may auto-send (e.g. interested, meeting_request)."
    },
    "min_confidence": {
      "type": "number",
      "description": "reply rules: classifier floor (default 0.8)."
    },
    "segment_id": {
      "type": "string",
      "description": "message rules: only members of this segment."
    },
    "channel": {
      "type": "string",
      "enum": [
        "email"
      ],
      "description": "message rules: which channel auto-sends (only 'email')."
    },
    "daily_cap": {
      "type": "number",
      "description": "Max auto-sends per day (default 10)."
    },
    "rule_id": {
      "type": "string",
      "description": "pause/resume/delete: the rule."
    }
  }
}

gtm_mailboxes

List the mailboxes connected to your account.

Full instructions for agents

Inventory of the user's sending surfaces: `connected` (their own Gmail, linked via Composio), `provisioned` (Vaaya-managed prewarmed mailboxes with warmup_day + daily_cap; empty until mailbox provisioning ships), and `connect_url` (send the user here to link an inbox). Use before planning email volume: connected inboxes ≈ 20-30 sends/day each; provisioned boxes carry their own daily_cap. Read-only, free.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

gtm_replies

Review incoming replies.

Full instructions for agents

List the prospect-reply drafts awaiting your approval (newest first). Each row carries `leadId`/`leadName` when the sender matches a lead in the repository (see gtm_leads). Free.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

gtm_reply_approve

Approve a prepared reply for sending.

Full instructions for agents

Approve a pending reply draft as-is and send it. Pass `message_id` (from gtm_replies). Sends from the user's own account; bills the send.

InputRequired?TypeDescription
message_idRequiredstringThe pending draft message id.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "The pending draft message id."
    }
  },
  "required": [
    "message_id"
  ]
}

gtm_reply_edit

Edit a prepared reply before it is sent.

Full instructions for agents

Edit a pending reply draft and send the edited text. Pass `message_id` and `text`. Sends from the user's own account and bills the send.

InputRequired?TypeDescription
message_idRequiredstringThe pending draft message id.
textRequiredstringThe replacement reply text to send.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "The pending draft message id."
    },
    "text": {
      "type": "string",
      "description": "The replacement reply text to send."
    }
  },
  "required": [
    "message_id",
    "text"
  ]
}

gtm_reply_reject

Reject a prepared reply.

Full instructions for agents

Reject a pending reply draft — discard it without sending. Pass `message_id`.

InputRequired?TypeDescription
message_idRequiredstringThe pending draft message id.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "The pending draft message id."
    }
  },
  "required": [
    "message_id"
  ]
}

brain_push

Save a fact to your company knowledge base.

Full instructions for agents

Add a fact to the COMPANY brain — the shared org knowledge graph every teammate's agent reads. Use when the user explicitly wants to save/remember something for their whole company/team (e.g. "save that Acme uses Salesforce to the company brain"). The fact is added DIRECTLY and immediately (no approval step). Only works for an active member of a company brain (a company-email-domain user who hasn't been removed); others get an error. Personal facts are captured automatically by `consult` — only use `brain_push` for deliberate company-wide knowledge. Pass `fact`. Free; returns { ok, message } or { ok:false, error }.

InputRequired?TypeDescription
factRequiredstringA self-contained statement to add to the company brain.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "fact": {
      "type": "string",
      "description": "A self-contained statement to add to the company brain."
    }
  },
  "required": [
    "fact"
  ]
}

worker_create

Create a recurring task that checks for new findings on a schedule.

Full instructions for agents

Create a WORKER: a standing job Vaaya runs on a schedule to watch the web and surface only what's NEW or changed, then notify. General-purpose — use it for anything that needs a constant eye on the internet. Each worker is named by its `kind`: a signaling system → 'signal worker', a job hunt → 'job search worker', anything else → 'custom worker'. Pass `query` (plain-English: what to watch for), `cadence` (how often), and `kind` (signal|job_search|research|custom — drives the name). Optional: `name` (override the auto name), `sources` (array of URLs — give URLs to watch those exact pages for changes; omit to do a recency web search), and `notify_slack_webhook` (a Slack incoming-webhook URL to ping with new findings). Findings appear on the Workers dashboard, deduped so you only hear about each thing once. Creating is free; each scheduled run spends from the user's balance under their workers daily budget. Returns { ok, worker_id }.

InputRequired?TypeDescription
queryRequiredstringPlain-English description of what to watch for.
cadenceRequiredstringHow often to run. Default every_6h. Sub-30m cadences (every_5m/every_15m) only tick that fast when the Fly reconciler poll is enabled; otherwise they run on the 30m cron.
kindOptionalstringTask type; names the worker '<kind> worker'. signal=funding/hiring/launch triggers, job_search=watch roles, research=async deep-research (parallel/task), custom=free-form (default).
nameOptionalstringOptional name override (default '<kind> worker').
sourcesOptionalarrayOptional URLs to watch for changes. Omit to do a recency web search.
signal_typesOptionalarrayFor kind:signal only — which buying-signal types to watch (default all).
sentimentOptionalarrayFor kind:signal only — keep only news with these sentiments (default: all). e.g. ["negative"] to watch for trouble at accounts.
high_signal_onlyOptionalbooleanFor kind:signal only — keep only high-relevance news articles (fewer, stronger findings).
notify_slack_webhookOptionalstringOptional Slack incoming-webhook URL to ping with new findings.
notify_emailOptionalstringOptional email address to send new-finding digests to (in addition to / instead of Slack). Delivery is a metered email send.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Plain-English description of what to watch for."
    },
    "cadence": {
      "type": "string",
      "enum": [
        "every_5m",
        "every_15m",
        "every_30m",
        "hourly",
        "every_6h",
        "daily",
        "weekly"
      ],
      "description": "How often to run. Default every_6h. Sub-30m cadences (every_5m/every_15m) only tick that fast when the Fly reconciler poll is enabled; otherwise they run on the 30m cron."
    },
    "kind": {
      "type": "string",
      "enum": [
        "signal",
        "job_search",
        "research",
        "custom"
      ],
      "description": "Task type; names the worker '<kind> worker'. signal=funding/hiring/launch triggers, job_search=watch roles, research=async deep-research (parallel/task), custom=free-form (default)."
    },
    "name": {
      "type": "string",
      "description": "Optional name override (default '<kind> worker')."
    },
    "sources": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional URLs to watch for changes. Omit to do a recency web search."
    },
    "signal_types": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "funding",
          "hiring",
          "launch",
          "leadership",
          "press"
        ]
      },
      "description": "For kind:signal only — which buying-signal types to watch (default all)."
    },
    "sentiment": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "positive",
          "negative",
          "neutral"
        ]
      },
      "description": "For kind:signal only — keep only news with these sentiments (default: all). e.g. [\"negative\"] to watch for trouble at accounts."
    },
    "high_signal_only": {
      "type": "boolean",
      "description": "For kind:signal only — keep only high-relevance news articles (fewer, stronger findings)."
    },
    "notify_slack_webhook": {
      "type": "string",
      "description": "Optional Slack incoming-webhook URL to ping with new findings."
    },
    "notify_email": {
      "type": "string",
      "description": "Optional email address to send new-finding digests to (in addition to / instead of Slack). Delivery is a metered email send."
    }
  },
  "required": [
    "query",
    "cadence"
  ]
}

worker_list

List your recurring tasks.

Full instructions for agents

List your workers with kind, status, cadence, last run, and finding counts. Read-only, free.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

worker_findings

Read findings from recurring tasks.

Full instructions for agents

List recent worker findings (newest first), optionally for one worker. Read-only, free. Pass optional `worker_id` and `limit` (default 50).

InputRequired?TypeDescription
worker_idOptionalstringRestrict to one worker (omit for all).
limitOptionalnumberMax findings to return (default 50).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "Restrict to one worker (omit for all)."
    },
    "limit": {
      "type": "number",
      "description": "Max findings to return (default 50)."
    }
  }
}

worker_pause

Pause a recurring task.

Full instructions for agents

Pause a worker so it stops running. Pass `worker_id`. Free.

InputRequired?TypeDescription
worker_idRequiredstringThe worker id (from worker_list).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "The worker id (from `worker_list`)."
    }
  },
  "required": [
    "worker_id"
  ]
}

worker_resume

Resume a paused task.

Full instructions for agents

Resume a paused worker. Pass `worker_id`. Free.

InputRequired?TypeDescription
worker_idRequiredstringThe worker id (from worker_list).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "The worker id (from `worker_list`)."
    }
  },
  "required": [
    "worker_id"
  ]
}

worker_delete

Delete a recurring task and its findings.

Full instructions for agents

Delete a worker and its findings. Pass `worker_id`. Free.

InputRequired?TypeDescription
worker_idRequiredstringThe worker id (from worker_list).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "worker_id": {
      "type": "string",
      "description": "The worker id (from `worker_list`)."
    }
  },
  "required": [
    "worker_id"
  ]
}

worker_run_now

Run a recurring task now.

Full instructions for agents

Run all your ACTIVE workers immediately instead of waiting for the next scheduled tick (spends from your balance under the workers daily budget). Returns a summary { workers, newFindings, spentCents }.

This tool has no named inputs. Check the schema for any additional requirements.

Full input schema (JSON)
{
  "type": "object",
  "properties": {}
}

trade_watchlist

Manage the tickers and themes on your research watchlist.

Full instructions for agents

Manage your trading watchlist — free-text tickers and themes. You see every digest idea either way; watchlist matches get highlighted, sorted first, and drive your alerts badge. `action='list'` (default) shows entries; `action='add'`/`action='remove'` take `kind` ('ticker' like AMAT/RELIANCE, or 'theme' like "semiconductors" or "rate cuts") and `value`. Themes also match Polymarket bet ideas. Free.

InputRequired?TypeDescription
actionOptionalstringDefaults to 'list'.
kindOptionalstringEntry kind (required for add/remove).
valueOptionalstringTicker symbol or theme phrase (required for add/remove).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "list",
        "add",
        "remove"
      ],
      "description": "Defaults to 'list'."
    },
    "kind": {
      "type": "string",
      "enum": [
        "ticker",
        "theme"
      ],
      "description": "Entry kind (required for add/remove)."
    },
    "value": {
      "type": "string",
      "description": "Ticker symbol or theme phrase (required for add/remove)."
    }
  }
}

trade_ideas

Read research ideas for your watchlist.

Full instructions for agents

Your trade-idea inbox from the daily 8:30 IST digest — grounded, cited stock ideas (entry zone, target, invalidation, horizon) and Polymarket bet ideas (YES/NO calls with entry odds and a resolve-by date). Everyone sees the full digest; entries matching your trade_watchlist are flagged via matchedOn. Optional `status` (fresh | taken | passed | resolved) and `kind` (stock | bet) filters. Includes the global track record (stocks and bets reported separately). Research only — NOT investment advice; no orders are placed. Free.

InputRequired?TypeDescription
statusOptionalstringFilter by your decision state or resolution. Omit for all.
kindOptionalstringFilter to stock ideas or prediction-market bets. Omit for both.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "fresh",
        "taken",
        "passed",
        "resolved"
      ],
      "description": "Filter by your decision state or resolution. Omit for all."
    },
    "kind": {
      "type": "string",
      "enum": [
        "stock",
        "bet"
      ],
      "description": "Filter to stock ideas or prediction-market bets. Omit for both."
    }
  }
}

trade_idea_act

Record your decision about a research idea.

Full instructions for agents

Record your decision on a trade idea from trade_ideas: `action='take'` (you executed it yourself at your broker) or `action='pass'`. Optional `note`. This feeds the digest's learning loop and your track record. It does NOT place any order. Free.

InputRequired?TypeDescription
idea_idRequiredstringThe idea id from trade_ideas.
actionRequiredstringYour decision.
noteOptionalstringOptional note (e.g. fill price, reason).
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "idea_id": {
      "type": "string",
      "description": "The idea id from trade_ideas."
    },
    "action": {
      "type": "string",
      "enum": [
        "take",
        "pass"
      ],
      "description": "Your decision."
    },
    "note": {
      "type": "string",
      "description": "Optional note (e.g. fill price, reason)."
    }
  },
  "required": [
    "idea_id",
    "action"
  ]
}

trade_ticker

Read the research collected for a ticker.

Full instructions for agents

The story so far on one stock: every digest idea you were matched on for `symbol`, newest first — thesis evolution, levels, outcomes. Research memory only; NOT investment advice. Free.

InputRequired?TypeDescription
symbolRequiredstringTicker symbol, e.g. AMAT or RELIANCE.
Full input schema (JSON)
{
  "type": "object",
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Ticker symbol, e.g. AMAT or RELIANCE."
    }
  },
  "required": [
    "symbol"
  ]
}