bank_id_validate
Validate bank routing identifiers offline (IBAN is covered by /v1/iban-validate): US ABA routing numbers (3-7-1 checksum, Federal Reserve district, thrift / electronic ranges), SWIFT / BIC (bank, ISO country, location, branch, test and passive BICs), Mexican CLABE (checksum, bank, plaza), Argenti...
This record as markdown: /tools/com-it-scorptech-x402/bank-id-validate.md
What bank_id_validate does on ScorpTech x402 API
AI agents call bank_id_validate to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | |
value | string | Yes |
Parameters from the server's own tool schema.
Why bank_id_validate is rated Low
Even though bank_id_validate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs bank_id_validate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bank_id_validate, this is the rule to start with:
bank_id_validate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every bank_id_validate call is checked against it from then on.
Questions about bank_id_validate
Validate bank routing identifiers offline (IBAN is covered by /v1/iban-validate): US ABA routing numbers (3-7-1 checksum, Federal Reserve district, thrift / electronic ranges), SWIFT / BIC (bank, ISO country, location, branch, test and passive BICs), Mexican CLABE (checksum, bank, plaza), Argentine CBU (both check digits), Canadian routing numbers (EFT 0YYYXXXXX and MICR XXXXX-YYY, institution names), UK sort codes, Australian BSB (bank and state) and Indian IFSC (bank). Auto-detects the type from the format. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/bank-id-validate. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
bank_id_validate accepts 2 parameters: type, value. Required: value. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for bank_id_validate: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
bank_id_validate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bank_id_validate rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for bank_id_validate. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
bank_id_validate is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue