Synthex Forge — x402 Paid Agent Services

Get Trusted Route

get_trusted_route

Read-onlyIdempotent

The specific routes an agent is cleared to call. use it rather than api_ebook_download for trusted route, not ebook download; an object with 43 fields including activity, agent. $0.3 USDC.

Input Schema

Name	Required	Description	Default
`routes`	No	The routes this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ts`	No	The `ts` field of the response.
`note`	No	A note on how the answer was produced.
`rank`	No	The `rank` field of the response.
`agent`	No	The `agent` field of the response.
`fails`	No	The `fails` field of the response.
`route`	No	The `route` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`events`	No	The `events` field of the response.
`sha256`	No	The `sha256` field of the response.
`framing`	No	The `framing` field of the response.
`metrics`	No	The `metrics` field of the response.
`outcome`	No	The `outcome` field of the response.
`ranking`	No	The `ranking` field of the response.
`verdict`	Yes	The decision this tool returned.
`activity`	No	The `activity` field of the response.
`disputes`	No	The `disputes` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`freshness`	No	The `freshness` field of the response.
`rationale`	No	The `rationale` field of the response.
`successes`	No	The `successes` field of the response.
`amount_usd`	No	The amount the operation concerned.
`best_route`	No	The `best_route` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`identifier`	No	The `identifier` field of the response.
`event_count`	No	The `event_count` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`ranked_count`	No	The `ranked_count` field of the response.
`routes_count`	No	The `routes_count` field of the response.
`success_rate`	No	The `success_rate` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`dispute_count`	No	The `dispute_count` field of the response.
`missingFields`	No	The `missingFields` field of the response.
`avg_amount_usd`	No	The `avg_amount_usd` field of the response.
`providedFields`	No	The `providedFields` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`figuresProvided`	No	The `figuresProvided` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`reputation_score`	No	The `reputation_score` field of the response.
`total_amount_usd`	No	The `total_amount_usd` field of the response.
`observed_outcomes`	No	The `observed_outcomes` field of the response.
`best_reputation_score`	No	The `best_reputation_score` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed45 schema fields changedOct 31, 2026

addedOutput schema / properties / activity

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

addedOutput schema / properties / agent

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / amount_usd

Added value: +{
+  "description": "The amount the operation concerned.",
+  "type": "number"
+}

addedOutput schema / properties / avg_amount_usd

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

addedOutput schema / properties / best_reputation_score

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

addedOutput schema / properties / best_route

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / dispute_count

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

addedOutput schema / properties / disputes

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / event_count

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

addedOutput schema / properties / events

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

addedOutput schema / properties / fails

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

addedOutput schema / properties / figuresProvided

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

addedOutput schema / properties / framing

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

addedOutput schema / properties / freshness

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

addedOutput schema / properties / identifier

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

addedOutput schema / properties / metrics

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

addedOutput schema / properties / missingFields

Added value: +{
+  "description": "The `missingFields` 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 / observed_outcomes

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

addedOutput schema / properties / outcome

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

addedOutput schema / properties / providedFields

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / rank

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

addedOutput schema / properties / ranked_count

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

addedOutput schema / properties / ranking

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

addedOutput schema / properties / rationale

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / reputation_score

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

addedOutput schema / properties / route

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

addedOutput schema / properties / routes_count

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signedBy

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

removedOutput schema / properties / status

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

addedOutput schema / properties / success_rate

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

addedOutput schema / properties / successes

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

addedOutput schema / properties / total_amount_usd

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

addedOutput schema / properties / ts

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verdictLevel

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the response shape ('object with 43 fields including activity, agent') and a cost of '$0.3 USDC,' which no annotation or schema field conveys and which matters for a metered call.

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?

It is short, but it reads as a run-on fragment with a semicolon splice and a price tacked onto the end rather than front-loaded. The core scope statement comes first, which is good, but the grammar and the trailing '$0.3 USDC' hurt scannability.

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?

With an output schema present, the description need not enumerate the 43 fields, and annotations cover safety, so the essentials are nearly there. What remains missing is how the single `routes` parameter should be populated and whether the call is scoped to one agent or all cleared routes, which an agent would need before invoking.

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?

There is a single optional `routes` parameter at 100% schema coverage, so the baseline is 3. The description does not clarify whether `routes` acts as a filter, a requested set, or an override, and it leaves that meaning entirely to the generic schema text ('See the schema for its type'), adding no value.

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 the resource and scope concretely: 'The specific routes an agent is cleared to call,' which tells an agent this is a read of authorized route data. It explicitly distinguishes itself from the nearest-sounding sibling, `api_ebook_download`, saying it is for 'trusted route, not ebook download.' The only weakness is the missing verb ('Get' appears solely in the name) and fragmentary phrasing.

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?

It names the alternative (`api_ebook_download`) and states the condition that selects this tool instead, so the agent can disambiguate without opening a schema. There are no explicit exclusions or prerequisites beyond that single contrast, which keeps it short of a 5.

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.