Validate an Aptos address before sending: format and normalization, reserved sys...

{ "method": "GET", "queryParams": { "address": "0x1" }, "type": "http" }

{ "example": { "address": "0x1", "address_type": "Aptos account address", "chain": "aptos", "chain_name": "Aptos", "checksum": "not_applicable", "detected_network": null, "format_valid": true, "network_match": true, "normalized": "0x0000000000000000000000000000000000000000000000000000000000000001", "note": "Verdict is advice for an agent before moving funds: ok = nothing found, caution = check first, do_not_send = a serious problem, invalid = not a usable Aptos address. The on-chain check reads a public node at the latest block. Sanctions screening covers OFAC-listed digital-currency addresses only. A valid, clean address can still belong to the wrong person: confirm it through a second channel and send a small test amount first for large transfers.", "on_chain": { "balance": 111.20868786, "balance_symbol": "APT", "checked": true, "exists": true, "kind": "account", "sequence_number": 0 }, "sanctions": { "checked": true, "entity": null, "list": "OFAC SDN digital-currency addresses", "sanctioned": false }, "source": "Computed locally (checksum and format); Aptos public node; OFAC SDN digital-currency address list", "summary": "Do not send without review: Aptos account address. This is a reserved Aptos framework address, not a user wallet. Funds sent to it are not recoverable.", "verdict": "do_not_send", "warnings": [ { "code": "no_checksum_format", "message": "This address format has no checksum, so a typo that still decodes is undetectable offline; the live check below helps, and a small test amount is the safest confirmation.", "severity": "low" }, { "code": "system_address", "message": "This is a reserved Aptos framework address, not a user wallet. Funds sent to it are not recoverable.", "severity": "high" } ] }, "type": "json" }