corpusAI Cloud Pricing

LLM token fixing

tokens_fixing

Read-onlyIdempotent

Paid (0.01 USDC per call). One day's token price fixing for a ticker such as CX.TOK.CLAUDESONNET5.IN. Median across every source and host at the standard tier (batch and free variants excluded). .IN and .OUT are input and output USD per million tokens; .BLEND is (3·input + output) / 4. CX.TOK.FRONTIER.<side> is the median across the frontier basket listed by /tokens/models.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	No	YYYY-MM-DD; default latest.
`ticker`	Yes	CX.TOK.<MODELCODE>.IN \| OUT \| BLEND, or CX.TOK.FRONTIER.<side>. Example: CX.TOK.FRONTIER.BLEND

Output Schema

TableJSON Schema

Name	Required	Description
`n`	Yes
`hi`	No
`lo`	No
`day`	Yes
`side`	No	One of: IN, OUT, BLEND
`unit`	No
`input`	No
`model`	No
`value`	Yes
`basket`	No
`output`	No
`ticker`	Yes
`members`	No
`methodology`	Yes

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": {
+    "basket": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "day": {
+      "type": "string"
+    },
+    "hi": {
+      "type": "number"
+    },
+    "input": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lo": {
+      "type": "number"
+    },
+    "members": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "methodology": {
+      "type": "string"
+    },
+    "model": {
+      "type": "string"
+    },
+    "n": {
+      "type": "number"
+    },
+    "output": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "side": {
+      "description": "One of: IN, OUT, BLEND",
+      "type": "string"
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "unit": {
+      "type": "string"
+    },
+    "value": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "ticker",
+    "day",
+    "methodology",
+    "value",
+    "n"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description goes further by disclosing the 0.01 USDC per-call cost, the median-across-sources aggregation method, and the standard-tier exclusion of batch/free variants. It stops short of noting wallet/auth requirements or any rate limits, but the cost and methodology disclosure is meaningful extra context.

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 cost and core operation are front-loaded, followed by the ticker grammar, with no filler sentences; every clause carries specification the agent needs. It is dense with notation but not redundant.

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?

An output schema exists, so return values need no explanation, and the description supplies the ticker vocabulary, aggregation semantics, tier restriction, and price. The one missing piece is sibling routing (when this fixing beats tokens_board/tokens_quotes), which is the only gap for an otherwise self-contained definition.

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, but the description adds real meaning beyond the schema by defining the units of `.IN`/`.OUT` (USD per million tokens), giving the exact `.BLEND` formula (3·input + output) / 4, and explaining that `CX.TOK.FRONTIER.<side>` is a median over the frontier basket from /tokens/models.

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 ('One day's token price fixing for a ticker') and even gives a concrete ticker example, so the agent knows exactly what is being computed. It does not explicitly distinguish itself from the many pricing siblings (tokens_board, tokens_history, tokens_quotes), leaving that differentiation to inference.

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?

Usage is only implied: a single-day fixing keyed by ticker, with batch and free tiers excluded. There is no explicit statement of when to reach for this instead of tokens_board/tokens_history/tokens_quotes, nor any when-not guidance, so the agent must infer the routing.

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.