Verify cryptocurrency wallet addresses for Bitcoin…
Verify cryptocurrency wallet addresses for Bitcoin (Base58Check/Bech32/Bech32m), Ethereum/EVM (EIP-55), Solana (Base58 32-byte), Tron, Dogecoin, and Litecoin
Request
- x-api-key: <your-api-key>
- Content-Type: application/json
Response
{
"addressDetails": {
"network": "Orange Polska",
"normalized": "PL61109010140000071219812874",
"rawInput": "PL61109010140000071219812874"
},
"isValid": true,
"status": "success",
"tokensDeducted": 1,
"validationResult": {
"addressType": "standard",
"chain": "<chain>",
"checksummedAddress": "Powstańców Śląskich 5/212, 53-332 Wrocław",
"encoding": "utf-8",
"isChecksummed": true,
"reason": "checksum ok"
}
}What it does
Verify cryptocurrency wallet addresses for Bitcoin (Base58Check/Bech32/Bech32m), Ethereum/EVM (EIP-55), Solana (Base58 32-byte), Tron, Dogecoin, and Litecoin
Request
Body
| Field | Type | Required | Description |
|---|---|---|---|
address | string | yes | The cryptocurrency wallet address to verify |
chain | enum | no | Target blockchain network or auto-detect One of: auto, bitcoin, ethereum, solana, tron, litecoin, dogecoin. |
Example request
{
"address": "Powstańców Śląskich 5/212, 53-332 Wrocław",
"chain": "auto"
}Response
| Field | Type | Description |
|---|---|---|
addressDetails | object | |
↳ network | string | |
↳ normalized | string | |
↳ rawInput | string | |
isValid | boolean | |
status | string | |
tokensDeducted | integer | |
validationResult | object | |
↳ addressType | string | |
↳ chain | string | |
↳ checksummedAddress | string | |
↳ encoding | string | |
↳ isChecksummed | boolean | |
↳ reason | string |
Example response
{
"addressDetails": {
"network": "Orange Polska",
"normalized": "PL61109010140000071219812874",
"rawInput": "PL61109010140000071219812874"
},
"isValid": true,
"status": "success",
"tokensDeducted": 1,
"validationResult": {
"addressType": "standard",
"chain": "<chain>",
"checksummedAddress": "Powstańców Śląskich 5/212, 53-332 Wrocław",
"encoding": "utf-8",
"isChecksummed": true,
"reason": "checksum ok"
}
}Errors
Every error answers with the same envelope: an HTTP status, a machine code and a sentence.
400 | The body or a parameter failed validation. The details array names the field. |
401 | No key, a revoked key or a wrong header. Send x-api-key. |
402 | The wallet cannot cover this call. Top up or wait for the monthly grant. |
404 | The resource does not exist, or it is not yours. Both answer identically and cost nothing. |
429 | Over the per-minute quota of your tier. Back off and retry. |
5xx | Upstream refused or timed out. The call is not billed. |
Code
curl -X POST 'https://app.castomapi.com/v1/verify/crypto-address' \
-H 'x-api-key: <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"address": "Powstańców Śląskich 5/212, 53-332 Wrocław", "chain": "auto"}'const res = await fetch('https://app.castomapi.com/v1/verify/crypto-address', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"address": "Powstańców Śląskich 5/212, 53-332 Wrocław", "chain": "auto"})
});
const data = await res.json();
console.log(data);import { request } from 'node:https';
// Node 18+ has fetch built in
const res = await fetch('https://app.castomapi.com/v1/verify/crypto-address', {
method: 'POST',
headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
body: JSON.stringify({"address": "Powstańców Śląskich 5/212, 53-332 Wrocław", "chain": "auto"})
});
const data = await res.json();
console.log(data);import requests
res = requests.post(
'https://app.castomapi.com/v1/verify/crypto-address',
headers={'x-api-key': '<your-api-key>'},
json={"address": "Powstańców Śląskich 5/212, 53-332 Wrocław", "chain": "auto"},
timeout=30,
)
print(res.json())<?php
$ch = curl_init('https://app.castomapi.com/v1/verify/crypto-address');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode(['address' => 'Powstańców Śląskich 5/212, 53-332 Wrocław', 'chain' => 'auto']),
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);Cost and limits
This operation needs no API key and costs nothing: called without a key it answers 200 and deducts zero tokens, up to 10 requests a minute per IP address.
Rate limits per minute
| No key | 10 |
| Free | 60 |
| Pro | 300 |
| Enterprise | 1200 |
Questions
What does Verify cryptocurrency wallet addresses for Bitcoin… cost?
This operation needs no API key and costs nothing: called without a key it answers 200 and deducts zero tokens, up to 10 requests a minute per IP address.
How do I authenticate?
Send your key in the x-api-key header. One key covers every metered endpoint; there is nothing to enable per endpoint.
Can I send an Authorization: Bearer token instead?
Not for a metered endpoint — those take the x-api-key header and nothing else. Bearer tokens belong to the account side: the dashboard and account APIs accept a JWT session, and castomapi-auth issues those through a standard OAuth2 handshake, with authorization code, client credentials and refresh grants. The auth service page covers it.
What are the limits?
10 requests a minute per IP with no key at all, 60 a minute on the free tier, 300 on Pro, 1200 on Enterprise. Above the no-key tier the quota is per account, across every endpoint.
OpenAPI: https://app.castomapi.com/docs/json