VEYA

veya_paid_call

Run one metered x402 resource call through the VEYA policy gate. Needs your VEYA apiKey, your Solana key (solanaPrivateKey, pays the USDC) and your Robinhood Chain key (robinhoodPrivateKey, signs the VEYA record and pays its ETH gas). Keys are used in memory for this call only and never stored. Before anything is signed VEYA checks the apiKey, both keys, your USDC and ETH balances, and the policy (tool, host, resource, network, asset, payee, per-call cap, task budget, input). It then pays, verifies the Solana payment at finalized, runs a 2-of-3 validator check, records a commitment on Robinhood Chain from your address and saves the run to your VEYA account. Every refusal returns decision blocked, a stable code and payment: null. The kill switch is operator-only; callers cannot change it. Allow at least 120 s for the tool call timeout.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "apiKey": "<apiKey>",
      "taskId": "<taskId>",
      "idempotencyKey": "<idempotencyKey>",
      "input": "<input>"
    },
    "name": "veya_paid_call"
  }
}

Input Schema

Name	Required	Description
`url`	No	Optional. Normally omit it and use resourceId; any URL outside the allowlist is blocked before payment.
`input`	Yes	Input fields for the resource, exactly as listed by veya_paid_discover (string values only).
`apiKey`	Yes	Your VEYA product API key (veya_dev_... or veya_live_...) from https://app.veyanet.tech (System -> API Keys). Every run is saved to this key's VEYA account.
`taskId`	Yes	Your task id. Calls with the same taskId share one task budget (per VEYA account).
`resourceId`	No	A resource id from veya_paid_discover, e.g. tokens.asset-risk-summary.
`idempotencyKey`	Yes	Unique per intended payment (per VEYA account). Repeating it returns the same run and never pays again; use a new key for a new payment.
`environmentUuid`	No	Optional VEYA environment on Veya.sol to record under (yours, from veya_register_environment). Defaults to the VEYA metered-call environment shown by veya_paid_discover.
`solanaPrivateKey`	No	Your own Solana wallet secret key (base58, or a JSON array of 64 numbers). It pays the USDC for this one call from your wallet. Used in memory only, never stored, logged or returned.
`taskBudgetAtomic`	No	Optional task budget in USDC atomic units (6 decimals, 10000 = 0.01 USDC). Defaults to the policy budget; cannot exceed the policy maximum.
`robinhoodPrivateKey`	No	Your own Robinhood Chain wallet private key (0x + 64 hex). It signs the VEYA record (storeCommitment on Veya.sol) and pays its small ETH gas, so the record comes from your address. Used in memory only, never stored, logged or returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / environmentUuid / description

Previous value: -"Optional VEYA environment on Veya.sol to record under (yours, from veya_register_environment). Defaults to the VEYA paid-call environment shown by veya_paid_discover."New value: +"Optional VEYA environment on Veya.sol to record under (yours, from veya_register_environment). Defaults to the VEYA metered-call environment shown by veya_paid_discover."

Changed1 schema field changedOct 25, 2026

changedInput schema / required

Previous value: -[
-  "apiKey",
-  "taskId",
-  "idempotencyKey",
-  "input",
-  "solanaPrivateKey",
-  "robinhoodPrivateKey"
-]New value: +[
+  "apiKey",
+  "taskId",
+  "idempotencyKey",
+  "input"
+]

Changed8 schema fields changedOct 25, 2026

addedInput schema / properties / apiKey

Added value: +{
+  "description": "Your VEYA product API key (veya_dev_... or veya_live_...) from https://app.veyanet.tech (System -> API Keys). Every run is saved to this key's VEYA account.",
+  "maxLength": 200,
+  "minLength": 10,
+  "type": "string"
+}

addedInput schema / properties / environmentUuid

Added value: +{
+  "description": "Optional VEYA environment on Veya.sol to record under (yours, from veya_register_environment). Defaults to the VEYA paid-call environment shown by veya_paid_discover.",
+  "pattern": "^[0-9a-fA-F]{8}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{4}-?[0-9a-fA-F]{12}$",
+  "type": "string"
+}

changedInput schema / properties / idempotencyKey / description

Previous value: -"Unique per intended payment. Repeating it returns the same run and never pays again; use a new key for a new payment."New value: +"Unique per intended payment (per VEYA account). Repeating it returns the same run and never pays again; use a new key for a new payment."

removedInput schema / properties / payerPrivateKey

Removed value: -{
-  "description": "Your own Solana wallet secret key (base58, or a JSON array of 64 numbers). It pays this one call from your wallet. Used in memory only, never stored or returned. Required on every call unless the server operator configured a payer.",
-  "maxLength": 1024,
-  "type": "string"
-}

addedInput schema / properties / robinhoodPrivateKey

Added value: +{
+  "description": "Your own Robinhood Chain wallet private key (0x + 64 hex). It signs the VEYA record (storeCommitment on Veya.sol) and pays its small ETH gas, so the record comes from your address. Used in memory only, never stored, logged or returned.",
+  "maxLength": 100,
+  "type": "string"
+}

addedInput schema / properties / solanaPrivateKey

Added value: +{
+  "description": "Your own Solana wallet secret key (base58, or a JSON array of 64 numbers). It pays the USDC for this one call from your wallet. Used in memory only, never stored, logged or returned.",
+  "maxLength": 1024,
+  "type": "string"
+}

changedInput schema / properties / taskId / description

Previous value: -"Your task id. Calls with the same taskId share one task budget."New value: +"Your task id. Calls with the same taskId share one task budget (per VEYA account)."

changedInput schema / required

Previous value: -[
-  "taskId",
-  "idempotencyKey",
-  "input"
-]New value: +[
+  "apiKey",
+  "taskId",
+  "idempotencyKey",
+  "input",
+  "solanaPrivateKey",
+  "robinhoodPrivateKey"
+]

Changed7 schema fields changedOct 25, 2026

addedInput schema / properties / idempotencyKey / description

Added value: +"Unique per intended payment. Repeating it returns the same run and never pays again; use a new key for a new payment."

addedInput schema / properties / input / description

Added value: +"Input fields for the resource, exactly as listed by veya_paid_discover (string values only)."

addedInput schema / properties / payerPrivateKey

Added value: +{
+  "description": "Your own Solana wallet secret key (base58, or a JSON array of 64 numbers). It pays this one call from your wallet. Used in memory only, never stored or returned. Required on every call unless the server operator configured a payer.",
+  "maxLength": 1024,
+  "type": "string"
+}

addedInput schema / properties / resourceId / description

Added value: +"A resource id from veya_paid_discover, e.g. tokens.asset-risk-summary."

addedInput schema / properties / taskBudgetAtomic / description

Added value: +"Optional task budget in USDC atomic units (6 decimals, 10000 = 0.01 USDC). Defaults to the policy budget; cannot exceed the policy maximum."

addedInput schema / properties / taskId / description

Added value: +"Your task id. Calls with the same taskId share one task budget."

addedInput schema / properties / url / description

Added value: +"Optional. Normally omit it and use resourceId; any URL outside the allowlist is blocked before payment."

AddedOct 24, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so thoroughly. It discloses key handling, policy checks, payment and verification sequence, refusal shape, kill-switch restrictions, and timeout expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, then efficiently covers requirements, checks, execution flow, refusal behavior, and timeout. Every sentence adds operational value for a complex payment tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is detailed enough for invocation, covering prerequisites, checks, sequence, and refusal behavior. However, with no output schema, it does not describe the successful response shape beyond saying the run is saved to the VEYA account.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters in detail. The description reinforces the roles of apiKey, solanaPrivateKey, and robinhoodPrivateKey, but it adds little meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Run one metered x402 resource call through the VEYA policy gate.' It is clear what the tool does, but it does not explicitly distinguish this from sibling tools such as veya_paid_run or veya_paid_discover.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operational context: required keys, preflight checks, payment flow, refusal behavior, and the 120 s timeout. It stops short of explicitly naming when to use this tool versus alternatives like veya_paid_run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VEYA tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.