BlockVectra: multi-chain RPC & Data API

Get Plans and Pricing

get_pricing

Read-only

Live prices and plan limits from GET /v1/plans. Use before estimating cost or when asked about free credits, rate limits or per-method prices. Units: 1 billing unit = pricing.cu_per_unit CU; 1 USD buys pricing.units_per_usd units. method_weights includes JSON-RPC and Data API CU per call, push.log / push.native_transfer / push.token_transfer per delivered data event, push.history per successful history request and push.address_day per billable address-day; resolve a method by exact match, then the longest prefix rule ending in *, then the * row (JSON-RPC only; Data API and push operations have no default). free.* values are in billing units; key_defaults are the free-account new-key default CU/s and burst CU; paid_key_minimums (when present, otherwise null or absent) are the paid-account per-key lower bounds in CU/s and burst CU — a floor, not a cap, and not any key's actual value (the first paid top-up raises each key to at least this floor and higher custom limits are kept; actual limits are per key in the console). promo.ends_at is a sign-up coverage cutoff, not the end of the offer. For a single method's chain support and documentation use get_method_info instead; for projecting cycle costs use estimate_usage instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "allOf": [
-      {
-        "properties": {
-          "free": {
-            "type": "object"
-          },
-          "key_defaults": {
-            "type": "object"
-          },
-          "method_weights": {
-            "type": "array"
-          },
-          "pricing": {
-            "type": "object"
-          }
-        },
-        "required": [
-          "pricing",
-          "method_weights"
-        ],
-        "type": "object"
-      },
-      {
-        "not": {
-          "properties": {
-            "error": {
-              "const": "invalid_tool_arguments",
-              "type": "string"
-            }
-          },
-          "required": [
-            "error"
-          ],
-          "type": "object"
-        }
-      }
-    ]
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "const": "invalid_tool_arguments",
-        "type": "string"
-      },
-      "message": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "reason": {
-        "enum": [
-          "invalid_root",
-          "schema_type",
-          "schema_enum",
-          "undeclared_property",
-          "credential_field",
-          "credential_value"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "reason",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "free": {
+            "type": "object"
+          },
+          "key_defaults": {
+            "type": "object"
+          },
+          "method_weights": {
+            "type": "array"
+          },
+          "paid_key_minimums": {
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "pricing": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "pricing",
+          "method_weights"
+        ],
+        "type": "object"
+      },
+      {
+        "not": {
+          "properties": {
+            "error": {
+              "const": "invalid_tool_arguments",
+              "type": "string"
+            }
+          },
+          "required": [
+            "error"
+          ],
+          "type": "object"
+        }
+      }
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "const": "invalid_tool_arguments",
+        "type": "string"
+      },
+      "message": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "invalid_root",
+          "schema_type",
+          "schema_enum",
+          "undeclared_property",
+          "credential_field",
+          "credential_value"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "reason",
+      "message"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedOct 18, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "free": {
+            "type": "object"
+          },
+          "key_defaults": {
+            "type": "object"
+          },
+          "method_weights": {
+            "type": "array"
+          },
+          "pricing": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "pricing",
+          "method_weights"
+        ],
+        "type": "object"
+      },
+      {
+        "not": {
+          "properties": {
+            "error": {
+              "const": "invalid_tool_arguments",
+              "type": "string"
+            }
+          },
+          "required": [
+            "error"
+          ],
+          "type": "object"
+        }
+      }
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "const": "invalid_tool_arguments",
+        "type": "string"
+      },
+      "message": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "invalid_root",
+          "schema_type",
+          "schema_enum",
+          "undeclared_property",
+          "credential_field",
+          "credential_value"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "reason",
+      "message"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "free": {
-    "type": "object"
-  },
-  "key_defaults": {
-    "type": "object"
-  },
-  "method_weights": {
-    "type": "array"
-  },
-  "pricing": {
-    "type": "object"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "pricing",
-  "method_weights"
-]

Changed3 schema fields changedSep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties
```
Removed value: -{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "free": {
+      "type": "object"
+    },
+    "key_defaults": {
+      "type": "object"
+    },
+    "method_weights": {
+      "type": "array"
+    },
+    "pricing": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "pricing",
+    "method_weights"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes far beyond them, disclosing unit semantics (1 unit = pricing.cu_per_unit CU), the exact method_weights resolution order (exact match, then longest prefix ending in '*', then the '*' row, with JSON-RPC vs Data API/push distinctions), and critical interpretation caveats such as paid_key_minimums being a floor rather than a cap and promo.ends_at being a sign-up coverage cutoff rather than the offer's end.

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

Conciseness4/5

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

Purpose and trigger are front-loaded in the first two sentences, and the subsequent technical detail is dense but mostly load-bearing (prefix-match rules, floor-vs-cap caveats). It is nonetheless long for a zero-param call, and some field enumeration overlaps with the existing output schema.

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

Completeness5/5

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

Output schema exists, so return values need not be narrated, yet the description still supplies the interpretive layer an agent needs (unit conversions, floor-not-cap, cutoff-not-offer-end). For a zero-param read-only pricing lookup, nothing material is missing.

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

Parameters4/5

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

Zero parameters, so per the rubric the baseline is 4. The description compensates richly by documenting the semantics of returned fields, but the 'parameter semantics' dimension has no parameters to add meaning to.

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

Purpose5/5

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

Opens with a specific verb+resource+source: 'Live prices and plan limits from GET /v1/plans'. It explicitly denies coverage of a sibling's domain ('For a single method's chain support and documentation use get_method_info instead'), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

States a concrete trigger ('Use before estimating cost or when asked about free credits, rate limits or per-method prices') and names two alternatives with the conditions that select them: get_method_info for a single method's chain support/docs, estimate_usage for cycle cost projection. Both when-to-use and when-not-to-use are covered.

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

All BlockVectra: multi-chain RPC & Data API 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.