agenteconomy.cloud

register

Supply-side registration: $5 / 30 days (x402, mcp-pricing-v1.1) for actions start and renew; actions challenge_response, status and update_spec are free. You pay to be EXAMINED (EIP-191 ownership challenge + endpoint 402-conformance + registration-v1.0.0 schema validation) and can pay and fail — the fee buys the examination, never the outcome. Presence in discover is never gated by registration, and tier/rank/verdicts never move with it: registration adds claims-labeled data. SPEND-CAP WARNING: $5 = 5000000 micro-USDC is above the $1 default per-call cap many x402 clients ship — raise your client cap for start/renew or it will refuse to sign. Flow: start (submit spec, pay, receive a 72h challenge) → challenge_response (submit the payTo key’s EIP-191 signature; the audit runs) → registered while paid_through holds. renew re-audits and extends 30 days; renewal grace 7 days after paid_through — the mark itself drops at paid_through exactly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "register"
  }
}

Input Schema

Name	Required	Description
`spec`	No	registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json
`action`	Yes	start and renew are paid ($5/30 days); challenge_response, status and update_spec are free
`seller`	No	0x… payTo address — alternative lookup where registration_id is not at hand
`signature`	No	challenge_response: EIP-191 personal_sign of the exact challenge_text by the payTo key — 0x + 130 hex (r\|\|s\|\|v). update_spec: same signer over the spec-update text (see signed_at)
`signed_at`	No	update_spec: ISO 8601 timestamp inside the signed text, within 15 minutes of server time — text: "agenteconomy.cloud spec update v1\nregistration_id: <id>\nspec_hash: <sha256 hex of the JCS-canonical new spec>\nsigned_at: <this value>"
`challenge_id`	No	challenge_response: optional; defaults to the latest issued challenge
`registration_id`	No	from start (all actions after start)

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations available, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It warns that the fee buys an examination, not an outcome, notes that a client can pay and fail, flags the $1 default x402 spend cap, and specifies challenge validity, renewal grace, and exact mark-drop timing.

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 description is dense but almost every sentence carries decision-critical operational information: pricing, spend-cap risk, action flow, challenge expiry, grace period, and discover independence. It is front-loaded with the most important facts, though the single unbroken flow paragraph would be easier to scan if structured as steps or bullets.

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 multi-action tool with seven parameters, no output schema, and no annotations, this description is exceptionally complete. It covers cost, failure semantics, client-side cap risk, action sequencing, challenge duration, renewal grace, and the exact paid_through drop behavior, leaving an agent with enough context to invoke the correct action.

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 flow-level meaning: which actions require payment, which parameters belong to challenge_response versus update_spec, and that registration_id comes from start. It enriches the schema more than it replaces it, with some duplication around payment status and EIP-191 signatures.

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?

The description opens with Supply-side registration and the x402 pricing model, immediately identifying the resource and action scope. It enumerates paid vs. free actions and explicitly separates itself from the discover sibling by stating that presence in discover is never gated by registration, giving an agent a clear identity for the tool.

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 gives explicit per-action guidance: start and renew are paid, the other actions are free, and the flow start to challenge_response to registered tells an agent what sequence to follow. It also provides a when-not condition for discover, but it does not directly contrast register with check, diagnose, or verify.

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

All agenteconomy.cloud 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.