Contract
{
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Ethereum address (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045)"
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"input": {
"type": "string",
"description": "The address text exactly as submitted, echoed back."
},
"valid": {
"type": "boolean",
"description": "Overall verdict: true only when the address is correctly formatted AND, if a mixed-case checksum is present, that checksum is valid."
},
"normalized": {
"type": "string",
"description": "The canonical EIP-55 checksummed form of the address. Observed identical to the input when the input was already correctly checksummed, and re-cased to the correct checksum when the input's casing was wrong -- this is the form to use going forward, not necessarily a copy of what was submitted."
},
"format_valid": {
"type": "boolean",
"description": "True when the address is a well-formed 0x-prefixed 40-hex-character string, independent of checksum casing."
},
"checksum_valid": {
"type": "boolean",
"description": "True when the address's mixed-case checksum matches EIP-55. Observed false on a format_valid address with a single altered hex character -- format_valid and checksum_valid are independent checks, not one gating the other."
},
"is_zero_address": {
"type": "boolean",
"description": "True when the address is the all-zero 0x000...000 null address."
},
"checksum_present": {
"type": "boolean",
"description": "True when the address uses mixed-case letters, i.e. carries a checksum to check."
}
},
"description": "The address validation result, as returned at routing.responseResultPath ($.output).",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.081081 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 23, 2026
