corpusAI Cloud Pricing

Index fixing

index_fixing

Read-onlyIdempotent

Paid (0.01 USDC per call). One day's fixing for a ticker: median USD per GPU-hour of eligible quotes, with low, high and count. Quote segments (MKT, AGG, NEO, INT, EXE, HYP) fix from that day's snapshots; the default day is the latest snapshot. SPOT fixes from the full UTC day of spot events, so the default is yesterday; SPOT composites carry per-region values and spread_vs_neo. See /methodology for eligibility and aggregation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	No	Fixing day, YYYY-MM-DD. Default: latest available.
`ticker`	Yes	Ticker from /index/tickers, e.g. `CX.H100SXM.NEO` or `CX.H100SXM.SPOT.US-EAST-1`. Example: CX.H100SXM.NEO

Output Schema

TableJSON Schema

Name	Required	Description
`n`	Yes	Quotes (or regions) behind the fixing.
`hi`	No
`lo`	No
`day`	Yes
`gpu`	No
`unit`	No
`value`	Yes	Median USD per GPU-hour of eligible quotes (or median across regions for SPOT composites).
`source`	No
`ticker`	Yes
`members`	No	Quote counts per provider/market.
`regions`	No	SPOT composites: per-region values.
`segment`	No
`instance`	No
`methodology`	Yes
`spread_vs_neo`	No	SPOT composite minus the latest NEO fixing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "day": {
+      "type": "string"
+    },
+    "gpu": {
+      "type": "string"
+    },
+    "hi": {
+      "type": "number"
+    },
+    "instance": {
+      "type": "string"
+    },
+    "lo": {
+      "type": "number"
+    },
+    "members": {
+      "additionalProperties": true,
+      "description": "Quote counts per provider/market.",
+      "properties": {},
+      "type": "object"
+    },
+    "methodology": {
+      "type": "string"
+    },
+    "n": {
+      "description": "Quotes (or regions) behind the fixing.",
+      "type": "number"
+    },
+    "regions": {
+      "description": "SPOT composites: per-region values.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "region": {
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "segment": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "spread_vs_neo": {
+      "description": "SPOT composite minus the latest NEO fixing.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    },
+    "value": {
+      "description": "Median USD per GPU-hour of eligible quotes (or median across regions for SPOT composites).",
+      "type": "number"
+    }
+  },
+  "required": [
+    "ticker",
+    "day",
+    "methodology",
+    "value",
+    "n"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses cost (0.01 USDC per call), the differing default-day semantics for quote segments vs SPOT, and the extra fields SPOT composites carry (per-region values, spread_vs_neo). These are real behavioral traits an agent needs before invoking, not restatements of the annotations.

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?

The pricing and core output definition are front-loaded, and every clause carries information. It is dense and slightly comma-heavy in the middle, but there is no filler.

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?

With annotations covering safety and an output schema present, the description needn't explain return shapes, and instead covers cost, defaults, and a methodology pointer. The only gap is any explicit routing to or from sibling tools.

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%, which sets a baseline of 3. The description adds genuine meaning: the 'day' default is not uniform – it is the latest snapshot for quote segments but yesterday for SPOT – which the schema's 'Default: latest available' does not capture.

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 resource and scope: 'One day's fixing for a ticker: median USD per GPU-hour of eligible quotes, with low, high and count.' It also differentiates quote segments (MKT, AGG, NEO, INT, EXE, HYP) from SPOT sources. It is not explicitly contrasted with siblings like index_board or index_history, which keeps it from a 5.

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

Usage Guidelines3/5

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

The description explains default-day behavior per source type (latest snapshot vs yesterday for SPOT) and points to /methodology, which is implicit usage guidance. However, it never says when to choose this tool over siblings such as index_board or index_history, so guidance is implied rather than stated.

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

All corpusAI Cloud Pricing 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.