Synthex Forge — x402 Paid Agent Services

Get Bestex Evidence

get_bestex_evidence

Read-onlyIdempotent

MiFID-style best-execution attestation. use it rather than create_sla_breach_evidence for bestex evidence, not sla breach evidence; an object with 89 fields including _diagnostics, arithmetic. $2 USDC.

Input Schema

Name	Required	Description
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`fills`	No	The fills this operation operates on. See the schema for its type and whether it is required.
`order`	No	The ordering the operation applies.
`benchmarks`	No	The benchmarks this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`bps`	No	The `bps` field of the response.
`asOf`	No	The `asOf` field of the response.
`code`	No	The `code` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`side`	No	The `side` field of the response.
`vwap`	No	The `vwap` field of the response.
`as_of`	No	The date the answer is computed as of.
`fills`	No	The `fills` field of the response.
`order`	No	The `order` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`reason`	No	Why the verdict was reached.
`source`	No	The `source` field of the response.
`symbol`	No	The `symbol` field of the response.
`arrival`	No	The `arrival` field of the response.
`primary`	No	The `primary` field of the response.
`verdict`	Yes	The decision this tool returned.
`defaults`	No	The `defaults` field of the response.
`findings`	No	The `findings` field of the response.
`notional`	No	The `notional` field of the response.
`readOnly`	No	The `readOnly` field of the response.
`verdicts`	No	The `verdicts` field of the response.
`hardRules`	No	The `hardRules` field of the response.
`parameter`	No	The `parameter` field of the response.
`side_sign`	No	The `side_sign` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_at`	No	The `signed_at` field of the response.
`signed_by`	No	The key id that signed the answer.
`vsVwapBps`	No	The `vsVwapBps` field of the response.
`arithmetic`	No	The `arithmetic` field of the response.
`benchmarks`	No	The `benchmarks` field of the response.
`provenance`	No	The `provenance` field of the response.
`public_key`	No	The `public_key` field of the response.
`assumptions`	No	The `assumptions` field of the response.
`methodology`	No	The `methodology` field of the response.
`slippageBps`	No	The `slippageBps` field of the response.
`sum_gap_bps`	No	The `sum_gap_bps` field of the response.
`sum_gap_usd`	No	The `sum_gap_usd` field of the response.
`vs_vwap_bps`	No	The `vs_vwap_bps` field of the response.
`_diagnostics`	No	The `_diagnostics` field of the response.
`coverageGaps`	No	The `coverageGaps` field of the response.
`fillNotional`	No	The `fillNotional` field of the response.
`qualityGrade`	No	The `qualityGrade` field of the response.
`slippage_bps`	No	The `slippage_bps` field of the response.
`sum_notional`	No	The `sum_notional` field of the response.
`toleranceBps`	No	The `toleranceBps` field of the response.
`vsArrivalBps`	No	The `vsArrivalBps` field of the response.
`arrival_price`	No	The `arrival_price` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`fill_notional`	No	The `fill_notional` field of the response.
`fill_quantity`	No	The `fill_quantity` field of the response.
`interval_vwap`	No	The `interval_vwap` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`quality_grade`	No	The `quality_grade` field of the response.
`requiredInput`	No	The `requiredInput` field of the response.
`timingRiskBps`	No	The `timingRiskBps` field of the response.
`tolerance_bps`	No	The `tolerance_bps` field of the response.
`decision_price`	No	The `decision_price` field of the response.
`executionPrice`	No	The `executionPrice` field of the response.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`total_quantity`	No	The `total_quantity` field of the response.
`vs_arrival_bps`	No	The `vs_arrival_bps` field of the response.
`benchmarkLadder`	No	The `benchmarkLadder` field of the response.
`execution_price`	No	The `execution_price` field of the response.
`timing_risk_bps`	No	The `timing_risk_bps` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`fill_sum_gap_bps`	No	The `fill_sum_gap_bps` field of the response.
`primaryBenchmark`	No	The `primaryBenchmark` field of the response.
`tolerance_source`	No	The `tolerance_source` field of the response.
`within_tolerance`	No	The `within_tolerance` field of the response.
`participationRate`	No	The `participationRate` field of the response.
`primary_benchmark`	No	The `primary_benchmark` field of the response.
`vsIntervalVwapBps`	No	The `vsIntervalVwapBps` field of the response.
`methodologyVersion`	No	The `methodologyVersion` field of the response.
`participation_rate`	No	The `participation_rate` field of the response.
`fillSumToleranceBps`	No	The `fillSumToleranceBps` field of the response.
`methodology_version`	No	Version of the method that produced the answer.
`quantity_convention`	No	The `quantity_convention` field of the response.
`signature_algorithm`	No	The `signature_algorithm` field of the response.
`secondary_benchmarks`	No	The `secondary_benchmarks` field of the response.
`vs_interval_vwap_bps`	No	The `vs_interval_vwap_bps` field of the response.
`primary_benchmark_bps`	No	The `primary_benchmark_bps` field of the response.
`primary_benchmark_price`	No	The `primary_benchmark_price` field of the response.
`implementationShortfallBps`	No	The `implementationShortfallBps` field of the response.
`implementation_shortfall_bps`	No	The `implementation_shortfall_bps` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed91 schema fields changedOct 31, 2026

addedOutput schema / properties / _diagnostics

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

addedOutput schema / properties / arithmetic

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

addedOutput schema / properties / arrival

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

addedOutput schema / properties / arrival_price

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

addedOutput schema / properties / asOf

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

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

addedOutput schema / properties / benchmarkLadder

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

addedOutput schema / properties / benchmarks

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

addedOutput schema / properties / bps

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

addedOutput schema / properties / canonicalization

Added value: +{
+  "description": "The canonicalisation rule the digest was computed under.",
+  "type": "string"
+}

addedOutput schema / properties / code

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

addedOutput schema / properties / coverageGaps

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / decision_price

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

addedOutput schema / properties / defaults

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / evidence_core

Added value: +{
+  "description": "The canonical, signed core of the answer — the payload the signature covers.",
+  "type": "object"
+}

addedOutput schema / properties / executionPrice

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

addedOutput schema / properties / execution_price

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

addedOutput schema / properties / fillNotional

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

addedOutput schema / properties / fillSumToleranceBps

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

addedOutput schema / properties / fill_notional

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

addedOutput schema / properties / fill_quantity

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

addedOutput schema / properties / fill_sum_gap_bps

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

addedOutput schema / properties / fills

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

addedOutput schema / properties / findings

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

addedOutput schema / properties / hardRules

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

addedOutput schema / properties / implementationShortfallBps

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

addedOutput schema / properties / implementation_shortfall_bps

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

addedOutput schema / properties / interval_vwap

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

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

addedOutput schema / properties / methodologyVersion

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

addedOutput schema / properties / methodology_version

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

addedOutput schema / properties / missing_fields

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

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

addedOutput schema / properties / order

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

addedOutput schema / properties / output_sha256

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

addedOutput schema / properties / parameter

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

addedOutput schema / properties / participationRate

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

addedOutput schema / properties / participation_rate

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

addedOutput schema / properties / primary

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

addedOutput schema / properties / primaryBenchmark

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

addedOutput schema / properties / primary_benchmark

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

addedOutput schema / properties / primary_benchmark_bps

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

addedOutput schema / properties / primary_benchmark_price

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

addedOutput schema / properties / profileVersion

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

addedOutput schema / properties / provenance

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

addedOutput schema / properties / public_key

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

addedOutput schema / properties / qualityGrade

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

addedOutput schema / properties / quality_grade

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

addedOutput schema / properties / quantity_convention

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

addedOutput schema / properties / readOnly

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / requiredInput

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

addedOutput schema / properties / secondary_benchmarks

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

addedOutput schema / properties / side

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

addedOutput schema / properties / side_sign

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

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

addedOutput schema / properties / signed_at

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

addedOutput schema / properties / signed_by

Added value: +{
+  "description": "The key id that signed the answer.",
+  "type": "string"
+}

addedOutput schema / properties / slippageBps

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

addedOutput schema / properties / slippage_bps

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

addedOutput schema / properties / source

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

removedOutput schema / properties / status

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

addedOutput schema / properties / sum_gap_bps

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

addedOutput schema / properties / sum_gap_usd

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

addedOutput schema / properties / sum_notional

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

addedOutput schema / properties / symbol

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

addedOutput schema / properties / timingRiskBps

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

addedOutput schema / properties / timing_risk_bps

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

addedOutput schema / properties / toleranceBps

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

addedOutput schema / properties / tolerance_bps

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

addedOutput schema / properties / tolerance_source

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

addedOutput schema / properties / total_quantity

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

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

addedOutput schema / properties / vsArrivalBps

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

addedOutput schema / properties / vsIntervalVwapBps

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

addedOutput schema / properties / vsVwapBps

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

addedOutput schema / properties / vs_arrival_bps

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

addedOutput schema / properties / vs_interval_vwap_bps

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

addedOutput schema / properties / vs_vwap_bps

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

addedOutput schema / properties / vwap

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

addedOutput schema / properties / within_tolerance

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: the return is an object with 89 fields including _diagnostics and arithmetic, and the call costs $2 USDC – a cost disclosure an agent cannot infer from the schema.

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?

Compact – essentially two clauses plus cost, with the purpose front-loaded. It loses a point for run-on semicolon splicing and a lowercase mid-sentence clause that make it read as notes rather than specification.

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?

With an output schema and full annotations already present, the description only needs to add what those cannot: the domain standard (MiFID), the sibling routing, and the monetary cost. All three are present, so an agent has enough to call it 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?

Schema description coverage is 100% and the as_of 'reproduce a past answer' semantics are already documented in the schema. The description adds no per-parameter meaning beyond that, 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?

Names a specific artifact – a MiFID-style best-execution attestation – which is distinct from generic evidence creation. It is clear what the tool produces, though the verb is implicit (the name says 'get' while the description frames it as producing an attestation), leaving minor ambiguity about whether it retrieves or generates.

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?

Explicitly routes the agent: 'use it rather than `create_sla_breach_evidence` for bestex evidence, not sla breach evidence.' That is a concrete when/when-not with a named alternative. The phrasing is grammatically awkward, but the selection signal is unambiguous.

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.