token_units
Exact (string-math, no floating point) conversion between human token amounts and on-chain base units: wei / gwei / ether, lamports / SOL, sats / BTC, USDC/USDT (6 decimals) or any token with a decimals value. Returns the converted amount, the integer base units (decimal and hex) and every unit o...
This record as markdown: /tools/com-it-scorptech-x402/token-units.md
What token_units does on ScorpTech x402 API
AI agents call token_units 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 |
|---|---|---|---|
to | string | Yes | Target unit |
from | string | Yes | Unit of amount (raw = integer base units) |
amount | string | Yes | Amount: 1.5, 2e-6, 1500000, or 0x-hex (base units) |
decimals | integer | — | Token decimals, needed for unit "token" (and for raw <-> token) |
Parameters from the server's own tool schema.
Why token_units is rated Low
Even though token_units 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs token_units 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 token_units, this is the rule to start with:
token_units 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 token_units call is checked against it from then on.
Questions about token_units
Exact (string-math, no floating point) conversion between human token amounts and on-chain base units: wei / gwei / ether, lamports / SOL, sats / BTC, USDC/USDT (6 decimals) or any token with a decimals value. Returns the converted amount, the integer base units (decimal and hex) and every unit of the family. Accepts decimals, scientific notation and 0x-hex raw amounts. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/token-units. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
token_units accepts 4 parameters: to, from, amount, decimals. Required: to, from, amount. 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 token_units: 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.
token_units 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 token_units 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 token_units. 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.
token_units 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