ChainHelix for Machines

agent_standing

The standing of one ERC-8004 agent on BNB Smart Chain from what it did, not what it declares: its evidence tier from the paid ERC-8183 hires ChainHelix funded and the delivery checks sealed on opBNB, whether it answers right now from the newest probe, and the feedback rows the registry holds for it graded by pattern (on BSC today they come from a rating farm). Every count carries its evidence: job ids, transactions, the registry read. Signed (EIP-191, the published ChainHelix statement signer), valid 24 hours. ChainHelix agents come back as first_party: evidence only, no verdict, no signature. Free without the signature at agents.chainhelix.io/standing/. Price: 2 cents per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	the ERC-8004 token id on BNB Smart Chain

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`now`	Yes
`name`	No
`page`	No
`tier`	Yes
`agent`	No
`error`	No
`owner`	No
`probe`	No
`verify`	No
`version`	No
`declared`	No
`nowMeans`	No
`paidHires`	No
`statement`	No
`tierMeans`	No
`firstParty`	No
`ownExample`	No
`howToVerify`	No
`sealedChecks`	No
`registryFeedback`	No
`permanentEvidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed3 schema fields changedOct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / meta

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "contentHash": {
-      "type": "string"
-    },
-    "generated": {
-      "type": "number"
-    },
-    "priceUsd": {
-      "type": "number"
-    },
-    "validUntil": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / receipt

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "bytes": {
-      "type": "number"
-    },
-    "covers": {
-      "type": "string"
-    },
-    "issuedAt": {
-      "type": "number"
-    },
-    "lookup": {
-      "type": "string"
-    },
-    "network": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "nonce": {
-      "type": "string"
-    },
-    "seq": {
-      "type": "number"
-    },
-    "settleTx": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sha256": {
-      "type": "string"
-    },
-    "tool": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "id": [
+    "Id",
+    "ID",
+    "@id"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab
```
Added value: +{
+  "id": "data.id"
+}
```

AddedSep 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

No annotations, so the description carries the full burden and does so well: EIP-191 signing with a published signer, 24-hour validity, a 2-cent per-call price, and the free unsigned fallback. It also discloses a non-obvious special case (ChainHelix agents return first_party with evidence only, no verdict or signature) and a data-quality caveat (feedback rows come from a rating farm on BSC).

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, evidence sources, signing and pricing are front-loaded, and nearly every clause carries information an agent needs (auth, cost, special-casing). It is a dense run-on sentence with stacked clauses, which hurts scannability, but little of the content is filler.

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 no explanation. The description still covers provenance of each count, the signature/auth model, validity window, pricing, and the first_party edge case — everything needed to decide and invoke correctly.

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

Parameters3/5

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

One parameter at 100% schema coverage, so the baseline is 3. The description's 'ERC-8004 agent' framing corroborates the schema's 'ERC-8004 token id on BNB Smart Chain' but adds no format, range or lookup semantics beyond it.

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 specific verb and resource ('the standing of one ERC-8004 agent on BNB Smart Chain') and immediately scopes it as evidence-based rather than self-declared. The singular 'one agent' plus the named evidence sources (ERC-8183 hires, opBNB delivery checks, newest probe, registry feedback rows) distinguish it cleanly from siblings like standing_bulk, standing_watch and verified_agents.

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?

Makes the single-agent scope explicit and offers the unsigned free alternative path (agents.chainhelix.io/standing/<id>), so an agent knows when this paid signed call is warranted. It does not explicitly name the bulk sibling as the alternative for many-id lookups, so a small routing gap remains.

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

All ChainHelix for Machines 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.

Resources

Need Help?