Synthex Forge — x402 Paid Agent Services

Search X402 Index

search_x402_index

Read-onlyIdempotent

The live index of paid x402 services, filterable by price. use it rather than create_x402_anchor for x402 index, not x402 anchor; an object with 32 fields including as_of, asset. $0.02 USDC.

Input Schema

Name	Required	Description
`limit`	No	Maximum results. Default 25, hard-clamped to 100.
`query`	No	Free-text capability match against the observed catalogue (path + summary + declared tags). Empty string = all. Supports a substring match and a token AND-match.
`network`	No	CAIP-2 network filter, e.g. 'eip155:8453'. Empty = any.
`max_price_usd`	No	Price ceiling in USD. An endpoint whose price we have NOT observed is EXCLUDED from a price-filtered query — an unknown price is not a cheap price.
`min_uptime_pct`	No	Uptime floor in percent. An endpoint we cannot yet score (fewer than 3 observations) is EXCLUDED — we do not guess.
`require_conformance`	No	When true, drop every endpoint whose conformance is 'insufficient_observations'.

Output Schema

Name	Required	Description
`host`	No	The `host` field of the response.
`note`	No	A note on how the answer was produced.
`path`	No	The `path` field of the response.
`as_of`	No	The date the answer is computed as of.
`asset`	No	The `asset` field of the response.
`count`	No	The `count` field of the response.
`limit`	No	The `limit` field of the response.
`stale`	No	The `stale` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`method`	No	The `method` field of the response.
`network`	No	The `network` field of the response.
`results`	No	The results the operation produced.
`summary`	No	One-line summary of the answer.
`targets`	No	The `targets` field of the response.
`verdict`	Yes	The decision this tool returned.
`networks`	No	The `networks` field of the response.
`verdicts`	No	The `verdicts` field of the response.
`last_seen`	No	The `last_seen` field of the response.
`price_usd`	No	The price of the operation that was paid.
`first_seen`	No	The `first_seen` field of the response.
`uptime_pct`	No	The `uptime_pct` field of the response.
`conformance`	No	The `conformance` field of the response.
`corpus_root`	No	The `corpus_root` field of the response.
`observations`	No	The `observations` field of the response.
`truthfulness`	No	The `truthfulness` field of the response.
`total_matched`	No	The `total_matched` field of the response.
`payable_observations`	No	The `payable_observations` field of the response.
`corpus_records_observed`	No	The `corpus_records_observed` field of the response.
`never_invents_endpoints`	No	The `never_invents_endpoints` field of the response.
`distinct_endpoints_known`	No	The `distinct_endpoints_known` field of the response.
`min_observations_for_a_score`	No	The `min_observations_for_a_score` field of the response.
`insufficient_observations_marker`	No	The `insufficient_observations_marker` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 31, 2026

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / asset

Added value: +{
+  "description": "The `asset` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / conformance

Added value: +{
+  "description": "The `conformance` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / corpus_records_observed

Added value: +{
+  "description": "The `corpus_records_observed` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / corpus_root

Added value: +{
+  "description": "The `corpus_root` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / count

Added value: +{
+  "description": "The `count` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / distinct_endpoints_known

Added value: +{
+  "description": "The `distinct_endpoints_known` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / first_seen

Added value: +{
+  "description": "The `first_seen` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / host

Added value: +{
+  "description": "The `host` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / insufficient_observations_marker

Added value: +{
+  "description": "The `insufficient_observations_marker` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / last_seen

Added value: +{
+  "description": "The `last_seen` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / limit

Added value: +{
+  "description": "The `limit` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / method

Added value: +{
+  "description": "The `method` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / min_observations_for_a_score

Added value: +{
+  "description": "The `min_observations_for_a_score` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / network

Added value: +{
+  "description": "The `network` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / networks

Added value: +{
+  "description": "The `networks` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / never_invents_endpoints

Added value: +{
+  "description": "The `never_invents_endpoints` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / observations

Added value: +{
+  "description": "The `observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / path

Added value: +{
+  "description": "The `path` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / payable_observations

Added value: +{
+  "description": "The `payable_observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / price_usd

Added value: +{
+  "description": "The price of the operation that was paid.",
+  "type": "number"
+}

addedOutput schema / properties / results

Added value: +{
+  "description": "The results the operation produced.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / stale

Added value: +{
+  "description": "The `stale` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / summary

Added value: +{
+  "description": "One-line summary of the answer.",
+  "type": "string"
+}

addedOutput schema / properties / targets

Added value: +{
+  "description": "The `targets` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / total_matched

Added value: +{
+  "description": "The `total_matched` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / truthfulness

Added value: +{
+  "description": "The `truthfulness` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / uptime_pct

Added value: +{
+  "description": "The `uptime_pct` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verdicts

Added value: +{
+  "description": "The `verdicts` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds a genuinely new behavioral fact: the call costs $0.02 USDC. That is the kind of cost signal an agent needs before invoking and is not present in any structured field. It loses a point for spending words on output shape ('32 fields including as_of, asset') instead of noting that unobserved prices or uptime are excluded from filtered queries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three fragments separated by semicolons, with the sibling-disambiguation clause buried mid-string and a dangling 'not x402 anchor' that reads like a drafting artifact. The output-field enumeration duplicates the output schema and does not earn its place. Front-loading of the core fact is fine, but the structure is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the '32 fields including as_of, asset' line is redundant rather than helpful. The cost disclosure and the sibling pointer partially compensate, but with 6 parameters and non-obvious exclusion rules, the description should explain that filtered queries silently drop endpoints with unknown price or uptime — the single biggest way an agent will misread the results.

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?

Schema description coverage is 100% and each of the six parameters carries a substantive description, including the important exclusion semantics for max_price_usd and min_uptime_pct. The description adds only the generic 'filterable by price', providing no meaning beyond the schema, so the baseline 3 applies.

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 opening clause identifies a specific resource ('the live index of paid x402 services') with a stated filter axis (price), which is enough to distinguish it from most siblings. It never uses a search verb and the fragmentary phrasing after the first sentence muddies rather than sharpens the purpose, so it falls short of a clean 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?

It does name an alternative ('use it rather than `create_x402_anchor`'), which is better than nothing, but the disambiguation is garbled ('for x402 index, not x402 anchor') and reads as a hedge rather than a rule. There is no guidance on when a price-filtered catalogue lookup is the right move versus siblings like get_x402_quote or get_agentic_commerce_index.

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

All Synthex Forge — x402 Paid Agent Services 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.