Skip to main content

Council of AI GSPC

by io.github.CSOAI-ORG

Overview Discussions Admin

Receipts batch (paid, x402; preview free)

receipts_batch

PAID (x402 or CSOAI LTD invoice). A historical batch of the estate's measurement receipts via https://councilof.ai/api/receipts/batch: every signed card-v0 leaf whose as_of falls in [from,to] (≤200), each with its Merkle inclusion path and the public root(s) that carried it, plus the root index for the window and one manifest card citing the batch sha256. Manifest signing is conditional: a returned unsigned manifest declares manifest_card.sig_ed25519:null and unsigned_reason, with signature unmeasured. Manifest root inclusion remains unmeasured. If signing throws after settlement, the route returns PAID_NOT_DELIVERED with no batch or manifest delivered; preserve the settlement receipt and reconcile before reissue, without automatically retrying or paying again. preview=true is free and returns count, span, root count and the sha256 of the exact bytes the paid call returns. Recent leaves are free at /root.json, /cards/ and /api/proof?sha= — the batch sells assembly across history, never a conclusion. This tool returns historical measurement leaves, not payment receipts. /api/receipts/latest reports aggregate receipt-store state when available; its counts do not verify a particular payment, delivery or buyer acceptance. Without x_payment the tool returns the 402 challenge.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Window end, ISO-8601. Defaults to now.
`from`	Yes	Window start, ISO-8601. Required.
`preview`	No	true = free: count, span, roots and batch sha256 without the leaves.
`x_payment`	No	The X-PAYMENT header value signed against accepts[] from the previous 402. Omit to receive the challenge.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	No
`route`	No
`status`	Yes	PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>
`accepts`	No
`resource`	No
`deliverable`	No
`http_status`	No
`x402Version`	No
`delivery_state`	No
`settlement_state`	No
`payment_presented`	No
`not_a_certification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
+  "properties": {
+    "accepts": {
+      "type": "array"
+    },
+    "deliverable": {},
+    "delivery_state": {
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "payment_presented": {
+      "type": "boolean"
+    },
+    "resource": {
+      "type": "object"
+    },
+    "route": {
+      "type": "string"
+    },
+    "settlement_state": {
+      "type": "string"
+    },
+    "status": {
+      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "x402Version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -{
-  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
-  "properties": {
-    "accepts": {
-      "type": "array"
-    },
-    "deliverable": {},
-    "delivery_state": {
-      "type": "string"
-    },
-    "http_status": {
-      "type": "integer"
-    },
-    "not_a_certification": {
-      "type": "boolean"
-    },
-    "payment_presented": {
-      "type": "boolean"
-    },
-    "resource": {
-      "type": "object"
-    },
-    "route": {
-      "type": "string"
-    },
-    "settlement_state": {
-      "type": "string"
-    },
-    "status": {
-      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
-      "type": "string"
-    },
-    "tool": {
-      "type": "string"
-    },
-    "x402Version": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "status"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
+  "properties": {
+    "accepts": {
+      "type": "array"
+    },
+    "deliverable": {},
+    "delivery_state": {
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "payment_presented": {
+      "type": "boolean"
+    },
+    "resource": {
+      "type": "object"
+    },
+    "route": {
+      "type": "string"
+    },
+    "settlement_state": {
+      "type": "string"
+    },
+    "status": {
+      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "x402Version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
-  "properties": {
-    "accepts": {
-      "type": "array"
-    },
-    "deliverable": {},
-    "delivery_state": {
-      "type": "string"
-    },
-    "http_status": {
-      "type": "integer"
-    },
-    "not_a_certification": {
-      "type": "boolean"
-    },
-    "payment_presented": {
-      "type": "boolean"
-    },
-    "resource": {
-      "type": "object"
-    },
-    "route": {
-      "type": "string"
-    },
-    "settlement_state": {
-      "type": "string"
-    },
-    "status": {
-      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
-      "type": "string"
-    },
-    "tool": {
-      "type": "string"
-    },
-    "x402Version": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "status"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
+  "properties": {
+    "accepts": {
+      "type": "array"
+    },
+    "deliverable": {},
+    "delivery_state": {
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "payment_presented": {
+      "type": "boolean"
+    },
+    "resource": {
+      "type": "object"
+    },
+    "route": {
+      "type": "string"
+    },
+    "settlement_state": {
+      "type": "string"
+    },
+    "status": {
+      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "x402Version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover only the coarse profile (readOnlyHint false, openWorldHint true, idempotentHint false, destructiveHint false). The description goes well beyond: conditional manifest signing with sig_ed25519:null and unsigned_reason, unmeasured root inclusion, the PAID_NOT_DELIVERED error path after settlement, and the instruction not to auto-retry or re-pay. This is exactly the operational context annotations cannot carry.

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 payment requirement and window scope are front-loaded, but the single dense paragraph also carries tangential content (e.g., the /api/receipts/latest aggregate-state disclaimer) that is not needed to invoke this tool. Length is defensible for the complexity, yet several clauses could be trimmed without loss.

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?

An output schema exists, so return values need not be described. Given the paid x402 flow, the free preview path, error semantics and the four parameters, the description supplies everything an agent needs to call, fail, and recover 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 still adds meaning by tying preview to the exact-byte sha256 the paid call would return and by describing the x_payment omission behavior as a 402 challenge, reinforcing the semantics beyond the field text.

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?

States a precise verb+resource: a historical batch of signed card-v0 measurement leaves within an [from,to] window, each with Merkle inclusion paths and roots plus a manifest card. It also draws an explicit boundary — 'This tool returns historical measurement leaves, not payment receipts' — distinguishing it from siblings like get_card, get_root, verify_inclusion and x402_trust.

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?

Explicitly says preview=true is free and what it returns, notes that recent leaves are free elsewhere (/root.json, /cards/, /api/proof?sha=) so the batch is only for assembly across history, and explains the x402 flow including the 402 challenge when x_payment is omitted. When-to-use, when-not-to-use, and the alternative routes are all present.

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

All Council of AI GSPC tools Inspect

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.

Resources