Validate a NEAR account before sending: named or implicit format, whether the ac...

{ "method": "GET", "queryParams": { "address": "near" }, "type": "http" }

{ "example": { "address": "near", "address_type": "NEAR named account", "chain": "near", "chain_name": "NEAR", "checksum": "not_applicable", "detected_network": null, "format_valid": true, "network_match": true, "normalized": "near", "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 NEAR 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": 69273.8341665785, "balance_symbol": "NEAR", "checked": true, "exists": true, "kind": "contract" }, "sanctions": { "checked": true, "entity": null, "list": "OFAC SDN digital-currency addresses", "sanctioned": false }, "source": "Computed locally (checksum and format); NEAR public node; OFAC SDN digital-currency address list", "summary": "Valid NEAR named account.", "verdict": "ok", "warnings": [] }, "type": "json" }