agent-embassy

Compute History

compute_history

Idempotent

GPU compute market history: paid time series over the Embassy's market-intelligence log of vast.ai public asks. Per-GPU cheapest/median/offer-count series or whole-market history, bounded and timestamped, embedded in your signed receipt. $0.25 per query via x402. Fully automated. Asks are ephemeral — re-observe before any decision.

MONETIZED VIA x402 — this tool is not callable for free. POST https://agent-embassy.fly.dev/v1/markets/compute/history with an x402 payment ($0.25, USDC on Base). Input schema: {"type":"object","properties":{"gpu":{"type":"string","description":"GPU class, e.g. 'H100 SXM'. Omit for whole-market history."},"limit":{"type":"number","description":"Max snapshots returned, 1-200 (default 50, oldest-first)."},"idempotency_key":{"type":"string","description":"Client-generated UUID; retries return the original receipt"},"agent_wallet":{"type":"string","description":"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."}},"required":["idempotency_key"]}

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	GPU class, e.g. 'H100 SXM'. Omit for whole-market history.
`limit`	No	Max snapshots returned, 1-200 (default 50, oldest-first).
`agent_wallet`	No	DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used.
`idempotency_key`	Yes	Client-generated UUID; retries return the original receipt

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. verified_check
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.15"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "description": "Settlement asset",
+      "type": "string"
+    },
+    "facilitator": {
+      "description": "x402 facilitator",
+      "type": "string"
+    },
+    "how": {
+      "description": "How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header",
+      "type": "string"
+    },
+    "networks": {
+      "description": "EVM CAIP-2 network ids accepted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "paid_url": {
+      "description": "x402-paid HTTPS URL to POST the tool inputs to",
+      "type": "string"
+    },
+    "payment_required": {
+      "const": true,
+      "description": "Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.",
+      "type": "boolean"
+    },
+    "price": {
+      "description": "Exact price, e.g. \"$0.15\"",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Tool name, e.g. verified_check",
+      "type": "string"
+    }
+  },
+  "required": [
+    "payment_required",
+    "tool",
+    "paid_url",
+    "price",
+    "networks",
+    "asset",
+    "facilitator",
+    "how"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 21, 2026

addedInput schema / properties / agent_wallet / description

Added value: +"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."

addedInput schema / properties / gpu / description

Added value: +"GPU class, e.g. 'H100 SXM'. Omit for whole-market history."

addedInput schema / properties / idempotency_key / description

Added value: +"Client-generated UUID; retries return the original receipt"

addedInput schema / properties / limit / description

Added value: +"Max snapshots returned, 1-200 (default 50, oldest-first)."

AddedSep 21, 2026

TDQS

A4.2/5.0

Behavior5/5

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

It discloses significant operational behavior beyond the annotations: the tool is monetized via x402 ($0.25 USDC on Base), requires a specific POST endpoint, is fully automated, returns data embedded in a signed receipt, and warns that asks are ephemeral. This goes well beyond the idempotent/readOnly/destructive hints and does not contradict them.

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

Conciseness3/5

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

The first paragraph is tight and informative, front-loading the core purpose, pricing, output, and ephemerality warning. However, the description then repeats the full input schema verbatim even though the structured input schema is already provided separately, which adds redundant length without new information.

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?

For a monetized tool, the description covers the critical invocation details: cost, currency, endpoint, method, idempotency behavior, dev-mode wallet behavior, and data freshness caveat. Since an output schema exists and the description explains the signed-receipt output, an agent has enough context to call the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds useful meaning by explaining the output series semantics (cheapest/median/offer-count), whole-market vs per-GPU history, and 'bounded and timestamped' nature. It does not radically improve on the schema, but it gives an agent a clearer mental model of what the parameters produce.

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 clearly identifies the resource (GPU compute market history over vast.ai asks) and the key modes (per-GPU cheapest/median/offer-count series or whole-market history). It is not a tautology, and 'history' naturally differentiates it from sibling tools like compute_spot_prices and compute_price_alerts, though it does not explicitly name those alternatives.

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 conveys clear context: this is a paid historical market-data query, and it explicitly warns that asks are ephemeral and should be re-observed before decisions. It stops short of naming when-not-to-use or routing to a specific sibling, so it earns strong but not perfect usage guidance.

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

All agent-embassy 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.