Skip to main content
Glama

Assurance Check

assurance_check
Idempotent

Use assurance_check for a go/no-go before your agent acts on a provider. Give the provider endpoint, the planned action, the amount at stake, and the permissions requested. We probe unpaid and return a signed ALLOW, ALLOW_WITH_RESTRICTIONS, ASK_HUMAN, REVERIFY, REROUTE, or QUARANTINE decision (or UNVERIFIED). Envelope only: trust_report. Cost and policy: preflight_check. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/assurance/check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action the agent intends to take, e.g. 'transfer' (required, max 200 chars)
contextNoOptional free-text context for the assessment (truncated to 2000 chars)
amount_usdcYesAmount at stake, as a positive decimal string, e.g. '0.25'
idempotency_keyYesIdempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.
provider_endpointYesHTTPS URL of the provider to assess (max 2000 chars; no credentials in URL)
permissions_requestedYesPermissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. ping
assetYesSettlement asset
priceYesExact price, e.g. "$0.05"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / price / description
      Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
  2. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  3. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."
  4. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"The action the agent intends to take, e.g. 'transfer' (required, max 200 chars)"
    • addedInput schema / properties / amount_usdc / description
      Added value: +"Amount at stake, as a positive decimal string, e.g. '0.25'"
    • addedInput schema / properties / context / description
      Added value: +"Optional free-text context for the assessment (truncated to 2000 chars)"
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."
    • addedInput schema / properties / permissions_requested / description
      Added value: +"Permissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars"
    • addedInput schema / properties / provider_endpoint / description
      Added value: +"HTTPS URL of the provider to assess (max 2000 chars; no credentials in URL)"
  5. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources