Synthex Forge — x402 Paid Agent Services

Assess Endpoint Verdict

assess_endpoint_verdict

Read-onlyIdempotent

Will this URL pay me if I call it?. use it rather than assess_service_verdict for verdict specifically; an object with 52 fields including algorithm, as_of. $0.02 USDC.

Input Schema

Name	Required	Description
`url`	Yes	The URL to fetch, verify or route to.
`window_hours`	No	How far back to look, in hours.
`expected_price_usd`	No	The expected price usd this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`ts`	No	The `ts` field of the response.
`now`	No	The `now` field of the response.
`url`	No	The `url` field of the response.
`kind`	No	The `kind` field of the response.
`as_of`	No	The date the answer is computed as of.
`route`	No	The `route` field of the response.
`value`	No	The `value` field of the response.
`by_key`	No	The `by_key` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`p95_ms`	No	The `p95_ms` field of the response.
`pay_to`	No	The `pay_to` field of the response.
`probes`	No	The `probes` field of the response.
`sha256`	No	The `sha256` field of the response.
`source`	No	The `source` field of the response.
`status`	No	The status of the operation.
`target`	No	The `target` field of the response.
`ts_raw`	No	The `ts_raw` field of the response.
`defects`	No	The `defects` field of the response.
`pay_tos`	No	The `pay_tos` field of the response.
`reasons`	No	The `reasons` field of the response.
`service`	No	The `service` field of the response.
`subject`	No	The `subject` field of the response.
`verdict`	Yes	The decision this tool returned.
`coverage`	No	How much of the underlying corpus the answer is based on.
`evidence`	No	The `evidence` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`price_usd`	No	The price of the operation that was paid.
`record_id`	No	The `record_id` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`disclaimer`	No	The `disclaimer` field of the response.
`latency_ms`	No	The `latency_ms` field of the response.
`public_key`	No	The `public_key` field of the response.
`risk_flags`	No	The `risk_flags` field of the response.
`uptime_30d`	No	The `uptime_30d` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`observations`	No	The `observations` field of the response.
`price_honest`	No	The `price_honest` field of the response.
`window_start`	No	The `window_start` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`last_probe_at`	No	The `last_probe_at` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`first_probe_at`	No	The `first_probe_at` field of the response.
`latency_samples`	No	The `latency_samples` field of the response.
`profile_version`	No	Version of the answer profile.
`minimum_required`	No	The `minimum_required` field of the response.
`observation_count`	No	The `observation_count` field of the response.
`price_accepts_usd`	No	The `price_accepts_usd` field of the response.
`declared_price_usd`	No	The `declared_price_usd` field of the response.
`price_declared_usd`	No	The `price_declared_usd` field of the response.
`consecutive_failures`	No	The `consecutive_failures` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed53 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / as_of

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

addedOutput schema / properties / by_key

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

addedOutput schema / properties / consecutive_failures

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

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the underlying corpus the answer is based on.",
+  "type": "object"
+}

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / declared_price_usd

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

addedOutput schema / properties / defects

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / disclaimer

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

addedOutput schema / properties / evidence

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

addedOutput schema / properties / first_probe_at

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

addedOutput schema / properties / key_id

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / last_probe_at

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

addedOutput schema / properties / latency_ms

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

addedOutput schema / properties / latency_samples

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

addedOutput schema / properties / minimum_required

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

addedOutput schema / properties / now

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

addedOutput schema / properties / observation_count

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

addedOutput schema / properties / observations

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

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / output_sha256

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "type": "string"
+}

addedOutput schema / properties / p95_ms

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

addedOutput schema / properties / pay_to

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

addedOutput schema / properties / pay_tos

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

addedOutput schema / properties / price_accepts_usd

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

addedOutput schema / properties / price_declared_usd

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

addedOutput schema / properties / price_honest

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

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

addedOutput schema / properties / profile_version

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / public_key

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

addedOutput schema / properties / reasons

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

addedOutput schema / properties / record_id

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

addedOutput schema / properties / risk_flags

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

addedOutput schema / properties / route

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

addedOutput schema / properties / service

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

addedOutput schema / properties / signed_over

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

addedOutput schema / properties / source

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

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

addedOutput schema / properties / subject

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

addedOutput schema / properties / target

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

addedOutput schema / properties / ts

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

addedOutput schema / properties / ts_raw

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

addedOutput schema / properties / uptime_30d

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

addedOutput schema / properties / url

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

addedOutput schema / properties / value

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / window_start

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "output_sha256",
+  "signature",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context the agent cannot get from annotations: a $0.02 USDC per-call cost and a rough shape of the payload (52 fields including algorithm and as_of). It loses a point because 'pay me' is never defined and there is no note on what happens when the answer is negative.

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?

Very short and front-loads the purpose question, but the phrasing is a fragment-riddled run-on ('...?. use it rather than...; an object with 52 fields...'). It is compact without being well structured; the cost figure is buried at the end rather than surfaced.

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

Completeness4/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 spelled out, and the description still gives cost, an alternative, and payload size. For a 3-parameter read tool this is nearly sufficient; the missing piece is a plain statement of what 'pay' and 'verdict' mean in this x402-style context.

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%, so url, window_hours, and expected_price_usd are already documented in the schema. The description adds no semantics about how window_hours interacts with expected_price_usd or how they affect the verdict, 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 question 'Will this URL pay me if I call it?' conveys a specific verb+resource (assess whether an endpoint is a paying counterparty) and explicitly distinguishes itself from assess_service_verdict. It falls short of 5 because it names only one of several near-identical assess_*_verdict siblings and never states plainly what a 'verdict' contains.

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?

Gives an explicit routing rule: use this rather than `assess_service_verdict` when you want the verdict specifically. No negative case or prerequisite is stated, and the other verdict siblings (assess_tool_verdict, assess_agent_verdict) go unaddressed, so it stops short of a full when/when-not matrix.

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.