Synthex Forge — x402 Paid Agent Services

Get Budget Preflight

get_budget_preflight

Read-onlyIdempotent

Budget Preflight. use it rather than get_quota_preflight for budget preflight, not quota preflight; an object with 29 fields including actionAmountUsd, agentId. $0.25 USDC.

Input Schema

Name	Required	Description
`policy`	No	The policy document or policy id the decision is evaluated against.
`agent_id`	No	The identifier of the agent the operation concerns.
`action_amount_usd`	No	The action amount 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.
`cap`	No	The `cap` field of the response.
`kind`	No	The `kind` field of the response.
`name`	No	The `name` field of the response.
`note`	No	A note on how the answer was produced.
`amount`	No	The `amount` field of the response.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`policy`	No	The `policy` field of the response.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`agentId`	No	The `agentId` field of the response.
`decision`	No	The `decision` field of the response.
`headroom`	No	The `headroom` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`daily_cap`	No	The `daily_cap` field of the response.
`decidedAt`	No	The `decidedAt` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`per_tx_cap`	No	The `per_tx_cap` field of the response.
`spent_today`	No	The `spent_today` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`evidenceDigest`	No	The `evidenceDigest` field of the response.
`actionAmountUsd`	No	The `actionAmountUsd` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`remainingBudgetUsd`	No	The `remainingBudgetUsd` field of the response.
`remaining_budget_usd`	No	The `remaining_budget_usd` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 31, 2026

addedOutput schema / properties / actionAmountUsd

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

addedOutput schema / properties / agentId

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

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / cap

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

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / daily_cap

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

addedOutput schema / properties / decidedAt

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

addedOutput schema / properties / decision

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / evidenceCore

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

addedOutput schema / properties / evidenceDigest

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

addedOutput schema / properties / headroom

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / name

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

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

addedOutput schema / properties / per_tx_cap

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

addedOutput schema / properties / policy

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / reason

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

addedOutput schema / properties / remainingBudgetUsd

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

addedOutput schema / properties / remaining_budget_usd

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

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` 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"
+}

addedOutput schema / properties / spent_today

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

removedOutput schema / properties / status

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

addedOutput schema / required
```
Added value: +[
+  "detail",
+  "ok"
+]
```

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 readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds useful non-annotation context: the $0.25 USDC cost and a high-level summary of the returned object.

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 the first sentence repeats the title and the '29 fields including actionAmountUsd, agentId' clause is redundant with the existing output schema. The useful routing and pricing information is present but the structure is choppy.

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 rich annotations, full schema coverage, and an output schema, the description only needs to add routing and purpose context. It supplies routing and cost, but it does not explain what decision or check a 'budget preflight' produces, leaving a core contextual gap.

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 the input schema already documents the three parameters. The description mentions actionAmountUsd and agentId, but in the context of the output object rather than clarifying input parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Budget Preflight', which merely restates the tool name/title and does not state a verb, resource, or outcome. The routing sentence distinguishes it from get_quota_preflight, but it still does not explain what the tool actually does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative get_quota_preflight and states when to use this tool instead: 'use it rather than get_quota_preflight for budget preflight, not quota preflight.' This gives a clear sibling-selection rule.

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.