Deterministic payment-destination preflight for agents, paid per call.
PayeeGuard checks where the money is about to go, while that is still a decision rather than a fact. It verifies the EIP-55 checksum a mixed-case address carries, compares the destination against the address you said you expected and reports the exact hex positions that differ, recognises the ground look-alikes used in address-poisoning attacks by their shared prefix and suffix rather than by edit distance alone, blocks burn sinks, precompiles and a token contract offered as its own payee, and says whether the destination can receive the asset at all. There is no model anywhere in it, and most of it is exact arithmetic on twenty bytes. Where the chain is needed and cannot answer, it returns unknown, because a confident guess about an irreversible transfer is worse than no answer.
| Route | What it does | Price |
|---|---|---|
POST /v1/guard/payee | Check a payment destination before the transfer becomes irreversible | $0.01 |
Send the request unpaid to see the live quote. You get HTTP 402 and a PAYMENT-REQUIRED header.
curl -i -sS -X POST https://payee.schemasure.com/v1/guard/payee \
-H 'content-type: application/json' \
-d '{"address":"0x7a3D40f7c6B18E5920Ab7C3e5d81f4A04E6F8a0D","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","expected_address":"0x7A3D9C1b5e2F4A8d6C0b3E5F7a9D1c2b4e6f8A0d"}'eip155:8453).Every response carries a verdict. When this service cannot determine an answer it returns
unknown with evidence explaining why. It never reports an undetermined result as a clean one.