19 deterministic validation tools for AI agents: IBAN, SWIFT/BIC, LEI, VAT, ABA routing, IFSC, ABN, Luhn, ISBN, E.164, SEDOL and company-number checks, plus rental due-diligence and batch/vendor-onboarding packs. Pay-per-call via x402 (gasless EIP-3009 USDC on Base); 20 free calls/day, no API key.
Scored across 24 tools
Most tools have a distinct angle, but there is real overlap: balance_check (native ETH + one ERC-20) vs erc20_balance both report token balances, and the composite tools (india_supplier_check, vendor_onboarding_pack) re-run checks that gstin_check/ifsc_check/iban_check/lei_check/vat_mod97_check already do individually. check_price, fx_spot_price_oracle and calculate_fx_savings are related pricing tools that an agent could confuse. Descriptions help, but boundaries are not clean.
All names are snake_case, which is good, but the ordering convention is mixed: noun_verb (balance_check, gstin_check, block_info, tx_activity) coexists with verb_noun (check_price, receipt_verify, batch_validate). Both styles are readable, but there is no single predictable pattern.
24 tools is at the heavy end of the 16-25 borderline band, and the set spans several loosely related domains (chain data, fiat/identity validation, pricing, receipts, scraping, schema validation). The composite tools add count without adding much distinct capability, pushing it toward over-provisioned.
The surface is broad and mostly self-consistent: chain data (balance, block, tx, token risk), pricing/quote flows, a wide set of structural validators, composite onboarding checks, and receipt verification. It covers the apparent 'deterministic checks rail' domain well, with only minor gaps (e.g., no name-based sanctions screening, no update/lifecycle operations, since it is read-only).
reconcile=reconcile_commerce(order:obj!,payments:arr!,delivery:obj?,certify:bool?)->XDR1ExceptionReport
| Name | Required | Description | Default |
|---|---|---|---|
| order | Yes | ||
| certify | No | ||
| delivery | No | ||
| payments | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden and largely fails it. It does disclose a return artifact (XDR1ExceptionReport), which weakly implies a report/exception-producing operation, but says nothing about mutability, side effects, certification semantics, permissions, or idempotency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single dense signature line with no wasted prose, but the terseness comes from under-specification rather than economy. Nothing is front-loaded because there is no explanation to front-load.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a four-parameter tool with nested objects, no annotations, and no output schema, the definition is wholly inadequate. An agent cannot determine the operation's semantics, side effects, or the meaning of any argument from this line alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for four parameters, two of them nested objects, so the description must compensate and does not. It merely repeats parameter names, types, and required/optional markers that the schema already encodes, without explaining what an order, payment set, delivery object, or certify flag actually mean or how they interact.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a type-signature line ('reconcile=reconcile_commerce(...)->XDR1ExceptionReport') that restates the tool name and its parameters rather than explaining what reconciliation does. The only new information is the return type XDR1ExceptionReport, which hints at a report-producing operation, but there is no verb-and-resource statement an agent could use to distinguish this from screen_entity, solvency_check, or verify_id.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no preconditions, and no mention of any alternative or sibling tool. The definition gives an agent no basis for choosing this tool over the other validation/compliance tools in the same family.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
screen_entity=screen_sanctions_exact(entity:str!,jurisdiction:str?,wallet:str?)->XDR1SanctionsVerdict
| Name | Required | Description | Default |
|---|---|---|---|
| entity | Yes | ||
| wallet | No | ||
| jurisdiction | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no auth requirements, no rate limits, no indication of what a verdict means or whether screening is cached/auditable. The only behavioral signal is the return type 'XDR1SanctionsVerdict', which hints at an output shape without explaining it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single terse line with no waste, but this is under-specification masquerading as conciseness. A signature dump is not an appropriately sized description for a screening tool with three parameters and no other documentation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter tool with no annotations, no output schema, and 0% parameter description coverage, the description is far too thin. The only compensating information is the implied return type, which does not substitute for usage, parameter, or behavioral context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it only restates parameter names with type and required/optional markers ('entity:str!', 'jurisdiction:str?', 'wallet:str?'). It adds no meaning for what a jurisdiction string should look like or how a wallet relates to entity screening.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The string conveys a specific verb+resource ('screen' against 'sanctions_exact'), so an agent can infer this performs exact-match sanctions screening rather than identity verification or solvency checks. However, it is presented as a raw signature rather than prose, and it never states what the screening actually does or returns in plain terms, so sibling differentiation is left largely to name-similarity guessing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as verify_id or reconcile. The name implies a sanctions-checking context, but nothing tells the agent when this tool is the right choice over its siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
solvency_check=balance_check(wallet:str!,asset:enum[USDC|EURC|ETH]?,min_minor:str?)->XDR1SolvencyProof
| Name | Required | Description | Default |
|---|---|---|---|
| asset | No | ||
| wallet | Yes | ||
| min_minor | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, yet it only implies a balance check and names a return type ('XDR1SolvencyProof'). It discloses nothing about permissions, rate limits, what the check evaluates against, or what 'solvency' means operationally.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is compact (one line, no waste), but the dense sigil notation ('str!', 'XDR1...') harms readability and is not front-loaded in a way an agent can quickly parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter financial tool with no annotations, 0% schema description coverage, and no output schema, the definition is far too sparse. Behavioral context, usage context, and parameter meaning are all missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate; it partially does by showing parameter names, types, the required marker on wallet, and enum values for asset (USDC|EURC|ETH) that the schema omits. However, it gives no meaning for 'min_minor' or the logic of the check, leaving semantics unclear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a cryptic pseudo-code equation ('solvency_check=balance_check(...)->XDR1SolvencyProof') that restates the tool name rather than stating in prose what the tool does. An agent can infer it relates to checking wallet balance/solvency, but the purpose is not clearly articulated and no sibling differentiation is offered.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no indication of when to use this tool versus the siblings (reconcile, screen_entity, verify_id), nor any preconditions or exclusions. The equation form gives no contextual guidance whatsoever.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
verify_id=verify_identifier(kind:enum[iban|lei|vat|gstin|ein|abn|duns|bic|isin|npi|uk_crn|eu_eori|other]!,id:str!,cc:str?)->XDR1Receipt
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | ||
| id | Yes | ||
| kind | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It signals that the call yields an 'XDR1Receipt', hinting at a verification result artifact, but says nothing about whether the operation is read-only, whether it hits an external authority or performs local checksum validation, error behavior for malformed IDs, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded line with no filler, which is appropriate for a compact signature-style entry. The terseness is the right instinct, though the ad-hoc notation ('!', '?', '->XDR1Receipt') trades readability for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, no annotations, and 0% schema description coverage, so the description is the only documentation an agent gets — and it is insufficient. It leaves the meaning of 'cc', per-kind ID formatting, and the nature of the returned receipt entirely unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description supplies real value by listing the 13 accepted 'kind' values (iban, lei, vat, gstin, ein, abn, duns, bic, isin, npi, uk_crn, eu_eori, other) and by marking required ('!') versus optional ('?') parameters. However, 'id' and 'cc' get only type annotations: it never explains that 'cc' is a country code, which kinds require it, or how the expected ID format varies by kind.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The entry is essentially the tool name expanded into a pseudo-signature ('verify_id=verify_identifier(...)'), which states a verb and a resource but adds little operational meaning about what verification actually entails. The kind enumeration shows the resource domain (IBAN, LEI, VAT, etc.), which helps, but the description never distinguishes this from siblings like screen_entity or solvency_check.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites, and no routing toward or away from the sibling tools (reconcile, screen_entity, solvency_check). The agent is left to infer from the name alone that this applies to formatted business/financial identifiers rather than entity names or solvency checks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
balance_checkbatch_validateblock_infocalculate_fx_savingscheck_priceclean_markdown_scrapercontext_distillcrypto_tickererc20_balancefx_spot_price_oraclegstin_checkiban_checkifsc_checkindia_supplier_checkinstant_json_schema_verifierlei_checkpre_disbursement_guardreceipt_verifyreconcilesanctions_address_screenscreen_entitysolvency_checkswift_bic_checktoken_contract_risktx_activityvat_mod97_checkvendor_onboarding_packverify_idpre_disbursement_guard2 fields changedInput schema / examplesPrevious value: -[
- {
- "company_number": "01234567",
- "declared_country": "GB",
- "invoice_amount_usd": 4500,
- "recipient_iban": "GB82WEST12345698765432",
- "vendor_domain": "billing@acme-consulting.co.uk"
- }
-]New value: +[
+ {
+ "company_number": "01234567",
+ "declared_country": "GB",
+ "invoice_amount_usd": 4500,
+ "prev_receipt_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
+ "recipient_iban": "GB82WEST12345698765432",
+ "vendor_domain": "billing@acme-consulting.co.uk"
+ }
+]Input schema / properties / prev_receipt_hashAdded value: +{
+ "description": "Preceding verification receipt hash (may also be passed via X-PREV-RECEIPT-HASH header).",
+ "type": "string"
+}sanctions_address_screen9 fields changedOutput schema / properties / blocklist_matchAdded value: +{
+ "type": [
+ "boolean",
+ "null"
+ ]
+}Output schema / properties / current_legal_statusAdded value: +{
+ "type": "string"
+}Output schema / properties / is_sanctioned / typePrevious value: -"boolean"New value: +"null"Output schema / properties / sanction_program / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / screening_statusAdded value: +{
+ "type": "string"
+}Output schema / properties / snapshot_sha256Added value: +{
+ "type": "string"
+}Output schema / properties / snapshot_statusAdded value: +{
+ "type": "string"
+}Output schema / properties / valid / typePrevious value: -"boolean"New value: +[
+ "boolean",
+ "null"
+]Output schema / requiredPrevious value: -[
- "tool",
- "valid",
- "is_sanctioned"
-]New value: +[
+ "tool",
+ "valid",
+ "is_sanctioned",
+ "blocklist_match",
+ "current_legal_status",
+ "screening_status"
+]clean_markdown_scraper12 fields changedInput schema / examplesPrevious value: -[
- {
- "html": "<h1>Protocol Overview</h1><p>Agentic non-custodial settlement gateway.</p><ul><li>Zero custody</li><li>Sub-cent fees</li></ul>"
- }
-]New value: +[
+ {
+ "url": "https://example.com/"
+ }
+]Input schema / properties / html / descriptionPrevious value: -"Raw HTML string to scrape and clean into pristine Markdown."New value: +"Raw HTML string to convert instead of fetching a URL (max 1 MiB). Provide exactly one of url or html."Input schema / properties / urlAdded value: +{
+ "description": "Public http(s) page to fetch (ports 80/443 only). Provide exactly one of url or html.",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "html"
-]New value: +[]Output schema / properties / codeAdded value: +{
+ "type": "string"
+}Output schema / properties / fetched_onAdded value: +{
+ "type": "string"
+}Output schema / properties / reasonAdded value: +{
+ "type": "string"
+}Output schema / properties / retryableAdded value: +{
+ "type": "boolean"
+}Output schema / properties / scopeAdded value: +{
+ "type": "string"
+}Output schema / properties / sourceAdded value: +{
+ "type": "object"
+}Output schema / properties / toolAdded value: +{
+ "type": "string"
+}Output schema / properties / validAdded value: +{
+ "type": "boolean"
+}token_contract_riskbalance_checkblock_infocalculate_fx_savingsclean_markdown_scrapercontext_distillcrypto_tickererc20_balancefx_spot_price_oracleinstant_json_schema_verifiertx_activityvat_mod97_check1 field changedInput schema / properties / vat_number / descriptionPrevious value: -"EU VAT id; BE mod-97 checksum (BE prefix optional)."New value: +"Belgian VAT id in the supported BE mod-97 format (BE prefix optional); not a VIES lookup."check_priceindia_supplier_check1 field changedInput schema / examplesPrevious value: -[
- {
- "gstin": "27AAPFU0939F1ZV",
- "ifsc": "HDFC0001234",
- "pan": "ABCDE1234F",
- "vpa": "merchant@okhdfcbank"
- }
-]New value: +[
+ {
+ "gstin": "27AAPFU0939F1ZV",
+ "ifsc": "HDFC0001234",
+ "pan": "AAACP1234M",
+ "vpa": "merchant@okhdfcbank"
+ }
+]aba_routing_checkabn_checkaci_trust_lookupafrica_supplier_checkassured_createassured_quotebalance_checkbind_insurance_policyblock_infocalculate_fx_savingschina_supplier_checkclean_markdown_scrapercnpj_checkcompany_number_formatcontext_distillcreate_ap2_pilotcreate_b2b_invoicecrypto_tickercsp_commitment_createdip_file_disputee164_checkean13_checkein_format_checkerc20_balancefx_spot_price_oracleget_b2b_invoicegulf_supplier_checkinstant_json_schema_verifierisbn_checkisin_checkiso20022_to_x402_intentiso20022_validateiso4217_currency_checkjapan_corp_checkjapan_supplier_checkkra_pin_checklatam_supplier_checklist_approved_insurersluhn_checkofac_sdn_checkpan_format_checkpod_verify_deliveryquote_3rd_party_insurancereconcilerent_deposit_guardrental_listing_riskrental_verdictrfc_checksanctions_address_screensedol_checksettlement_history_checksimulate_spend_sentineltx_activityuae_trn_checkupi_vpa_checkuscc_checkaba_routing_check2 fields changedInput schema / properties / routingAdded value: +{
+ "description": "9-digit US bank routing number (alias).",
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "aba_routing"
-]aci_trust_lookupafrica_supplier_checkassured_createassured_quotebind_insurance_policycalculate_fx_savingschina_supplier_checkclean_markdown_scrapercnpj_check1 field changedInput schema / properties / cnpj / descriptionPrevious value: -"14-digit Brazilian CNPJ (punctuation optional)."New value: +"14-digit Brazilian CNPJ; punctuation allowed (e.g. 00.000.000/0001-91)."create_ap2_pilotcreate_b2b_invoicecsp_commitment_createdip_file_disputeerc20_balance1 field changedInput schema / properties / decimals / descriptionPrevious value: -"Token decimals override (optional; default: on-chain decimals(), else common list, else 18)."New value: +"Token decimals override (optional)."fx_spot_price_oracleget_b2b_invoicegulf_supplier_checkindia_supplier_checkinstant_json_schema_verifieriso20022_to_x402_intent18 fields changedInput schema / examplesPrevious value: -[
- {
- "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
- }
-]New value: +[
+ {
+ "instruction": {
+ "creditor": {
+ "iban": "DE77100100100123456789"
+ },
+ "debtor": {
+ "iban": "DE89370400440532013000"
+ },
+ "end_to_end_id": "E2E-1001",
+ "instructed_amount": {
+ "amount_minor": "250000000",
+ "amount_str": "250.00",
+ "currency": "USD"
+ }
+ },
+ "seller_pay_to_address": "0xc59c85e661d34084a7769f955d17fd38254a6235"
+ }
+]Input schema / properties / chain_idAdded value: +{
+ "description": "Target chain ID (default 8453 for Base)",
+ "type": "number"
+}Input schema / properties / counterparty_wallet_directoryAdded value: +{
+ "description": "Enterprise IBAN -> 0x Base L2 wallet address map",
+ "type": "object"
+}Input schema / properties / instructionAdded value: +{
+ "description": "Validated BAP-1 payment instruction object",
+ "type": "object"
+}Input schema / properties / seller_pay_to_addressAdded value: +{
+ "description": "Fallback recipient Base L2 address",
+ "type": "string"
+}Input schema / properties / xmlRemoved value: -{
- "description": "ISO 20022 XML string (< 512KB).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "xml"
-]New value: +[
+ "instruction"
+]Output schema / properties / intent_templateAdded value: +{
+ "type": "object"
+}Output schema / properties / noticeAdded value: +{
+ "type": "string"
+}Output schema / properties / okAdded value: +{
+ "type": "boolean"
+}Output schema / properties / scopeRemoved value: -{
- "type": "string"
-}Output schema / properties / standardAdded value: +{
+ "type": "string"
+}Output schema / properties / statusAdded value: +{
+ "type": "string"
+}Output schema / properties / swapped_railRemoved value: -{
- "type": "string"
-}Output schema / properties / toolRemoved value: -{
- "type": "string"
-}Output schema / properties / validRemoved value: -{
- "type": "boolean"
-}Output schema / properties / x402_intentRemoved value: -{
- "type": "object"
-}Output schema / requiredPrevious value: -[
- "valid"
-]New value: +[
+ "ok",
+ "standard",
+ "intent_template",
+ "status"
+]iso20022_validate22 fields changedInput schema / examplesPrevious value: -[
- {
- "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
- }
-]New value: +[
+ {
+ "raw_payload": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.09\"><CstmrCdtTrfInitn><GrpHdr><MsgId>MSG-2026-001</MsgId><NbOfTxs>1</NbOfTxs><CtrlSum>100.00</CtrlSum></GrpHdr><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">100.00</InstdAmt></Amt><CdtrAgt><FinInstnId><BICFI>DEUTDEDDFXX</BICFI></FinInstnId></CdtrAgt><CdtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
+ }
+]Input schema / properties / formatAdded value: +{
+ "description": "'xml' or 'json' (default auto-detected)",
+ "type": "string"
+}Input schema / properties / namespaceAdded value: +{
+ "description": "Expected ISO 20022 schema namespace (e.g. 'pain.001.001.09')",
+ "type": "string"
+}Input schema / properties / raw_payloadAdded value: +{
+ "description": "Raw ISO 20022 XML or JSON message text",
+ "type": "string"
+}Input schema / properties / transactionsAdded value: +{
+ "description": "Structured transactions array for JSON validation",
+ "type": "array"
+}Input schema / properties / xmlRemoved value: -{
- "description": "ISO 20022 XML string (< 512KB).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "xml"
-]New value: +[
+ "raw_payload"
+]Output schema / properties / amountRemoved value: -{
- "type": "string"
-}Output schema / properties / ctrl_sum_minorAdded value: +{
+ "type": "string"
+}Output schema / properties / currencyRemoved value: -{
- "type": "string"
-}Output schema / properties / findingsAdded value: +{
+ "type": "array"
+}Output schema / properties / message_idAdded value: +{
+ "type": "string"
+}Output schema / properties / message_typeRemoved value: -{
- "type": "string"
-}Output schema / properties / namespaceAdded value: +{
+ "type": "string"
+}Output schema / properties / okAdded value: +{
+ "type": "boolean"
+}Output schema / properties / reasonRemoved value: -{
- "type": "string"
-}Output schema / properties / receipt_digestAdded value: +{
+ "type": "string"
+}Output schema / properties / scopeRemoved value: -{
- "type": "string"
-}Output schema / properties / standardAdded value: +{
+ "type": "string"
+}Output schema / properties / toolRemoved value: -{
- "type": "string"
-}Output schema / properties / tx_countAdded value: +{
+ "type": "number"
+}Output schema / requiredPrevious value: -[
- "valid"
-]New value: +[
+ "ok",
+ "standard",
+ "valid"
+]iso4217_currency_checkjapan_corp_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "corporate_number": "1010001008844"
- }
-]New value: +[
+ {
+ "number": "1180301018771"
+ }
+]Input schema / properties / corporate_numberRemoved value: -{
- "description": "13-digit Japanese Corporate Number.",
- "type": "string"
-}Input schema / properties / numberAdded value: +{
+ "description": "13-digit Japanese Corporate Number (e.g. 1180301018771).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "corporate_number"
-]New value: +[
+ "number"
+]japan_supplier_checkkra_pin_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "kra_pin": "P051123456Z"
- }
-]New value: +[
+ {
+ "pin": "P051112223Z"
+ }
+]Input schema / properties / kra_pinRemoved value: -{
- "description": "11-character Kenyan KRA PIN.",
- "type": "string"
-}Input schema / properties / pinAdded value: +{
+ "description": "11-character KRA PIN (e.g. P051112223Z).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "kra_pin"
-]New value: +[
+ "pin"
+]latam_supplier_checklist_approved_insurersofac_sdn_checkpan_format_checkpod_verify_deliverypre_disbursement_guardquote_3rd_party_insurancereceipt_verifyreconcilerfc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "rfc": "ABC680524P76"
- }
-]New value: +[
+ {
+ "rfc": "BBA830831LJ2"
+ }
+]Input schema / properties / rfc / descriptionPrevious value: -"12 or 13 character Mexican RFC."New value: +"12 or 13 character Mexican RFC (e.g. BBA830831LJ2)."simulate_spend_sentineluae_trn_checkupi_vpa_checkuscc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "uscc": "91310000775785552W"
- }
-]New value: +[
+ {
+ "uscc": "91330100799655058B"
+ }
+]Input schema / properties / uscc / descriptionPrevious value: -"18-character Chinese USCC code."New value: +"18-character Chinese Unified Social Credit Code (e.g. 91330100799655058B)."aba_routing_check2 fields changedInput schema / properties / routingRemoved value: -{
- "description": "9-digit US bank routing number (alias).",
- "type": "string"
-}Input schema / requiredAdded value: +[
+ "aba_routing"
+]aci_trust_lookupautonomous_commercial_pipelinebind_insurance_policybrowse_compute_clustersbrowse_technical_studiosbrowse_top_guildscalculate_fx_savingsclean_markdown_scrapercnpj_check1 field changedInput schema / properties / cnpj / descriptionPrevious value: -"14-digit Brazilian CNPJ; punctuation allowed (e.g. 00.000.000/0001-91)."New value: +"14-digit Brazilian CNPJ (punctuation optional)."create_ap2_pilotcreate_b2b_invoicecsp_commitment_createdip_file_disputeengine_benchmarkerc20_balance1 field changedInput schema / properties / decimals / descriptionPrevious value: -"Token decimals override (optional)."New value: +"Token decimals override (optional; default: on-chain decimals(), else common list, else 18)."fx_spot_price_oracleget_b2b_invoiceget_guild_profileget_studio_profileinstant_json_schema_verifieriso20022_to_x402_intent18 fields changedInput schema / examplesPrevious value: -[
- {
- "instruction": {
- "creditor": {
- "iban": "DE77100100100123456789"
- },
- "debtor": {
- "iban": "DE89370400440532013000"
- },
- "end_to_end_id": "E2E-1001",
- "instructed_amount": {
- "amount_minor": "250000000",
- "amount_str": "250.00",
- "currency": "USD"
- }
- },
- "seller_pay_to_address": "0xc59c85e661d34084a7769f955d17fd38254a6235"
- }
-]New value: +[
+ {
+ "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
+ }
+]Input schema / properties / chain_idRemoved value: -{
- "description": "Target chain ID (default 8453 for Base)",
- "type": "number"
-}Input schema / properties / counterparty_wallet_directoryRemoved value: -{
- "description": "Enterprise IBAN -> 0x Base L2 wallet address map",
- "type": "object"
-}Input schema / properties / instructionRemoved value: -{
- "description": "Validated BAP-1 payment instruction object",
- "type": "object"
-}Input schema / properties / seller_pay_to_addressRemoved value: -{
- "description": "Fallback recipient Base L2 address",
- "type": "string"
-}Input schema / properties / xmlAdded value: +{
+ "description": "ISO 20022 XML string (< 512KB).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "instruction"
-]New value: +[
+ "xml"
+]Output schema / properties / intent_templateRemoved value: -{
- "type": "object"
-}Output schema / properties / noticeRemoved value: -{
- "type": "string"
-}Output schema / properties / okRemoved value: -{
- "type": "boolean"
-}Output schema / properties / scopeAdded value: +{
+ "type": "string"
+}Output schema / properties / standardRemoved value: -{
- "type": "string"
-}Output schema / properties / statusRemoved value: -{
- "type": "string"
-}Output schema / properties / swapped_railAdded value: +{
+ "type": "string"
+}Output schema / properties / toolAdded value: +{
+ "type": "string"
+}Output schema / properties / validAdded value: +{
+ "type": "boolean"
+}Output schema / properties / x402_intentAdded value: +{
+ "type": "object"
+}Output schema / requiredPrevious value: -[
- "ok",
- "standard",
- "intent_template",
- "status"
-]New value: +[
+ "valid"
+]iso20022_validate22 fields changedInput schema / examplesPrevious value: -[
- {
- "raw_payload": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.09\"><CstmrCdtTrfInitn><GrpHdr><MsgId>MSG-2026-001</MsgId><NbOfTxs>1</NbOfTxs><CtrlSum>100.00</CtrlSum></GrpHdr><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">100.00</InstdAmt></Amt><CdtrAgt><FinInstnId><BICFI>DEUTDEDDFXX</BICFI></FinInstnId></CdtrAgt><CdtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
- }
-]New value: +[
+ {
+ "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
+ }
+]Input schema / properties / formatRemoved value: -{
- "description": "'xml' or 'json' (default auto-detected)",
- "type": "string"
-}Input schema / properties / namespaceRemoved value: -{
- "description": "Expected ISO 20022 schema namespace (e.g. 'pain.001.001.09')",
- "type": "string"
-}Input schema / properties / raw_payloadRemoved value: -{
- "description": "Raw ISO 20022 XML or JSON message text",
- "type": "string"
-}Input schema / properties / transactionsRemoved value: -{
- "description": "Structured transactions array for JSON validation",
- "type": "array"
-}Input schema / properties / xmlAdded value: +{
+ "description": "ISO 20022 XML string (< 512KB).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "raw_payload"
-]New value: +[
+ "xml"
+]Output schema / properties / amountAdded value: +{
+ "type": "string"
+}Output schema / properties / ctrl_sum_minorRemoved value: -{
- "type": "string"
-}Output schema / properties / currencyAdded value: +{
+ "type": "string"
+}Output schema / properties / findingsRemoved value: -{
- "type": "array"
-}Output schema / properties / message_idRemoved value: -{
- "type": "string"
-}Output schema / properties / message_typeAdded value: +{
+ "type": "string"
+}Output schema / properties / namespaceRemoved value: -{
- "type": "string"
-}Output schema / properties / okRemoved value: -{
- "type": "boolean"
-}Output schema / properties / reasonAdded value: +{
+ "type": "string"
+}Output schema / properties / receipt_digestRemoved value: -{
- "type": "string"
-}Output schema / properties / scopeAdded value: +{
+ "type": "string"
+}Output schema / properties / standardRemoved value: -{
- "type": "string"
-}Output schema / properties / toolAdded value: +{
+ "type": "string"
+}Output schema / properties / tx_countRemoved value: -{
- "type": "number"
-}Output schema / requiredPrevious value: -[
- "ok",
- "standard",
- "valid"
-]New value: +[
+ "valid"
+]iso4217_currency_checkjapan_corp_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "number": "1180301018771"
- }
-]New value: +[
+ {
+ "corporate_number": "1010001008844"
+ }
+]Input schema / properties / corporate_numberAdded value: +{
+ "description": "13-digit Japanese Corporate Number.",
+ "type": "string"
+}Input schema / properties / numberRemoved value: -{
- "description": "13-digit Japanese Corporate Number (e.g. 1180301018771).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "number"
-]New value: +[
+ "corporate_number"
+]kra_pin_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "pin": "P051112223Z"
- }
-]New value: +[
+ {
+ "kra_pin": "P051123456Z"
+ }
+]Input schema / properties / kra_pinAdded value: +{
+ "description": "11-character Kenyan KRA PIN.",
+ "type": "string"
+}Input schema / properties / pinRemoved value: -{
- "description": "11-character KRA PIN (e.g. P051112223Z).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "pin"
-]New value: +[
+ "kra_pin"
+]list_approved_insurersofac_sdn_checkpan_format_checkpod_verify_deliverypre_disbursement_guardquote_3rd_party_insurancequote_compute_slicerfc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "rfc": "BBA830831LJ2"
- }
-]New value: +[
+ {
+ "rfc": "ABC680524P76"
+ }
+]Input schema / properties / rfc / descriptionPrevious value: -"12 or 13 character Mexican RFC (e.g. BBA830831LJ2)."New value: +"12 or 13 character Mexican RFC."semantic_service_matchmakersimulate_spend_sentineluae_trn_checkupi_vpa_checkuscc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "uscc": "91330100799655058B"
- }
-]New value: +[
+ {
+ "uscc": "91310000775785552W"
+ }
+]Input schema / properties / uscc / descriptionPrevious value: -"18-character Chinese Unified Social Credit Code (e.g. 91330100799655058B)."New value: +"18-character Chinese USCC code."aba_routing_check2 fields changedInput schema / properties / routingAdded value: +{
+ "description": "9-digit US bank routing number (alias).",
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "aba_routing"
-]aci_trust_lookupautonomous_commercial_pipelinebind_insurance_policybrowse_compute_clustersbrowse_technical_studiosbrowse_top_guildscalculate_fx_savingsclean_markdown_scrapercnpj_check1 field changedInput schema / properties / cnpj / descriptionPrevious value: -"14-digit Brazilian CNPJ (punctuation optional)."New value: +"14-digit Brazilian CNPJ; punctuation allowed (e.g. 00.000.000/0001-91)."create_ap2_pilotcreate_b2b_invoicecsp_commitment_createdip_file_disputeengine_benchmarkerc20_balance1 field changedInput schema / properties / decimals / descriptionPrevious value: -"Token decimals override (optional; default: on-chain decimals(), else common list, else 18)."New value: +"Token decimals override (optional)."fx_spot_price_oracleget_b2b_invoiceget_guild_profileget_studio_profileinstant_json_schema_verifieriso20022_to_x402_intent18 fields changedInput schema / examplesPrevious value: -[
- {
- "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
- }
-]New value: +[
+ {
+ "instruction": {
+ "creditor": {
+ "iban": "DE77100100100123456789"
+ },
+ "debtor": {
+ "iban": "DE89370400440532013000"
+ },
+ "end_to_end_id": "E2E-1001",
+ "instructed_amount": {
+ "amount_minor": "250000000",
+ "amount_str": "250.00",
+ "currency": "USD"
+ }
+ },
+ "seller_pay_to_address": "0xc59c85e661d34084a7769f955d17fd38254a6235"
+ }
+]Input schema / properties / chain_idAdded value: +{
+ "description": "Target chain ID (default 8453 for Base)",
+ "type": "number"
+}Input schema / properties / counterparty_wallet_directoryAdded value: +{
+ "description": "Enterprise IBAN -> 0x Base L2 wallet address map",
+ "type": "object"
+}Input schema / properties / instructionAdded value: +{
+ "description": "Validated BAP-1 payment instruction object",
+ "type": "object"
+}Input schema / properties / seller_pay_to_addressAdded value: +{
+ "description": "Fallback recipient Base L2 address",
+ "type": "string"
+}Input schema / properties / xmlRemoved value: -{
- "description": "ISO 20022 XML string (< 512KB).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "xml"
-]New value: +[
+ "instruction"
+]Output schema / properties / intent_templateAdded value: +{
+ "type": "object"
+}Output schema / properties / noticeAdded value: +{
+ "type": "string"
+}Output schema / properties / okAdded value: +{
+ "type": "boolean"
+}Output schema / properties / scopeRemoved value: -{
- "type": "string"
-}Output schema / properties / standardAdded value: +{
+ "type": "string"
+}Output schema / properties / statusAdded value: +{
+ "type": "string"
+}Output schema / properties / swapped_railRemoved value: -{
- "type": "string"
-}Output schema / properties / toolRemoved value: -{
- "type": "string"
-}Output schema / properties / validRemoved value: -{
- "type": "boolean"
-}Output schema / properties / x402_intentRemoved value: -{
- "type": "object"
-}Output schema / requiredPrevious value: -[
- "valid"
-]New value: +[
+ "ok",
+ "standard",
+ "intent_template",
+ "status"
+]iso20022_validate22 fields changedInput schema / examplesPrevious value: -[
- {
- "xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03\"><CstmrCdtTrfInitn><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">5000.00</InstdAmt></Amt><CdtrAcct><Id><IBAN>GB82WEST12345698765432</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
- }
-]New value: +[
+ {
+ "raw_payload": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pain.001.001.09\"><CstmrCdtTrfInitn><GrpHdr><MsgId>MSG-2026-001</MsgId><NbOfTxs>1</NbOfTxs><CtrlSum>100.00</CtrlSum></GrpHdr><PmtInf><CdtTrfTxInf><Amt><InstdAmt Ccy=\"USD\">100.00</InstdAmt></Amt><CdtrAgt><FinInstnId><BICFI>DEUTDEDDFXX</BICFI></FinInstnId></CdtrAgt><CdtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>"
+ }
+]Input schema / properties / formatAdded value: +{
+ "description": "'xml' or 'json' (default auto-detected)",
+ "type": "string"
+}Input schema / properties / namespaceAdded value: +{
+ "description": "Expected ISO 20022 schema namespace (e.g. 'pain.001.001.09')",
+ "type": "string"
+}Input schema / properties / raw_payloadAdded value: +{
+ "description": "Raw ISO 20022 XML or JSON message text",
+ "type": "string"
+}Input schema / properties / transactionsAdded value: +{
+ "description": "Structured transactions array for JSON validation",
+ "type": "array"
+}Input schema / properties / xmlRemoved value: -{
- "description": "ISO 20022 XML string (< 512KB).",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "xml"
-]New value: +[
+ "raw_payload"
+]Output schema / properties / amountRemoved value: -{
- "type": "string"
-}Output schema / properties / ctrl_sum_minorAdded value: +{
+ "type": "string"
+}Output schema / properties / currencyRemoved value: -{
- "type": "string"
-}Output schema / properties / findingsAdded value: +{
+ "type": "array"
+}Output schema / properties / message_idAdded value: +{
+ "type": "string"
+}Output schema / properties / message_typeRemoved value: -{
- "type": "string"
-}Output schema / properties / namespaceAdded value: +{
+ "type": "string"
+}Output schema / properties / okAdded value: +{
+ "type": "boolean"
+}Output schema / properties / reasonRemoved value: -{
- "type": "string"
-}Output schema / properties / receipt_digestAdded value: +{
+ "type": "string"
+}Output schema / properties / scopeRemoved value: -{
- "type": "string"
-}Output schema / properties / standardAdded value: +{
+ "type": "string"
+}Output schema / properties / toolRemoved value: -{
- "type": "string"
-}Output schema / properties / tx_countAdded value: +{
+ "type": "number"
+}Output schema / requiredPrevious value: -[
- "valid"
-]New value: +[
+ "ok",
+ "standard",
+ "valid"
+]iso4217_currency_checkjapan_corp_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "corporate_number": "1010001008844"
- }
-]New value: +[
+ {
+ "number": "1180301018771"
+ }
+]Input schema / properties / corporate_numberRemoved value: -{
- "description": "13-digit Japanese Corporate Number.",
- "type": "string"
-}Input schema / properties / numberAdded value: +{
+ "description": "13-digit Japanese Corporate Number (e.g. 1180301018771).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "corporate_number"
-]New value: +[
+ "number"
+]kra_pin_check4 fields changedInput schema / examplesPrevious value: -[
- {
- "kra_pin": "P051123456Z"
- }
-]New value: +[
+ {
+ "pin": "P051112223Z"
+ }
+]Input schema / properties / kra_pinRemoved value: -{
- "description": "11-character Kenyan KRA PIN.",
- "type": "string"
-}Input schema / properties / pinAdded value: +{
+ "description": "11-character KRA PIN (e.g. P051112223Z).",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "kra_pin"
-]New value: +[
+ "pin"
+]list_approved_insurersofac_sdn_checkpan_format_checkpod_verify_deliverypre_disbursement_guardquote_3rd_party_insurancequote_compute_slicerfc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "rfc": "ABC680524P76"
- }
-]New value: +[
+ {
+ "rfc": "BBA830831LJ2"
+ }
+]Input schema / properties / rfc / descriptionPrevious value: -"12 or 13 character Mexican RFC."New value: +"12 or 13 character Mexican RFC (e.g. BBA830831LJ2)."semantic_service_matchmakersimulate_spend_sentineluae_trn_checkupi_vpa_checkuscc_check2 fields changedInput schema / examplesPrevious value: -[
- {
- "uscc": "91310000775785552W"
- }
-]New value: +[
+ {
+ "uscc": "91330100799655058B"
+ }
+]Input schema / properties / uscc / descriptionPrevious value: -"18-character Chinese USCC code."New value: +"18-character Chinese Unified Social Credit Code (e.g. 91330100799655058B)."cnpj_checkiso20022_to_x402_intentiso20022_validatejapan_corp_checkkra_pin_checkrfc_checkuscc_check
Add one secure layer between your agents and this server.