77trust / 100

Normalize

by Address normalisation in Onchain & crypto

x402 APIPassing, checked 49 min ago

Normalise an address to its canonical form — Ethereum to its EIP-55 checksummed form, bech32 Bitcoin to lowercase (base58check is left untouched as it is case-sensitive). An address that is not a valid address of a known chain is rejected before payment.

POST
https://wallet.openverbs.com/v1/normalize
Price
$0.004
per call in USDC
Uptime
100%
last 30 days
Response time
572 ms
720 ms slowest 5%
Last check
Passed
49 min ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://wallet.openverbs.com/v1/normalize

Each call costs $0.004 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://wallet.openverbs.com/v1/normalize
content-type: application/json

{
  "address": "0x52908400098527886E0F7030069857D2E4169EE7",
  "chain": "ethereum"
}

Parameters

ParameterTypeRequiredDescription
addressstringYesThe address to normalise.
chainstringNoOptional chain hint. One of: ethereum, bitcoin.

Example response

The listing has no example response.

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.004.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://wallet.openverbs.com/v1/normalize' \
  -H 'content-type: application/json' \
  --data-raw '{"address":"0x52908400098527886E0F7030069857D2E4169EE7","chain":"ethereum"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://wallet.openverbs.com/v1/normalize' \
  -H 'content-type: application/json' \
  --data-raw '{"address":"0x52908400098527886E0F7030069857D2E4169EE7","chain":"ethereum"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.004 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.004" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.004 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwallet.openverbs.com%2Fv1%2Fnormalize&method=POST
const res = await pay("https://wallet.openverbs.com/v1/normalize", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "address": "0x52908400098527886E0F7030069857D2E4169EE7",
    "chain": "ethereum"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.004 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.004"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://wallet.openverbs.com/v1/normalize",
        json={
            "address": "0x52908400098527886E0F7030069857D2E4169EE7",
            "chain": "ethereum",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
49 min agoPassed402549 ms$0.004
6 h agoPassed402600 ms$0.004
11 h agoPassed402583 ms$0.004
16 h agoPassed402577 ms$0.004
20 h agoPassed402602 ms$0.004
Show 10 older checks
25 h agoPassed402577 ms$0.004
30 h agoPassed402562 ms$0.004
34 h agoPassed402572 ms$0.004
39 h agoPassed402556 ms$0.004
43 h agoPassed402633 ms$0.004
47 h agoPassed402562 ms$0.004
2 days agoPassed402590 ms$0.004
2 days agoPassed402548 ms$0.004
3 days agoPassed402591 ms$0.004
3 days agoPassed402171 ms$0.004