Payee check
Check a payee before you sign a mandate
The agent does not pick a payee, so the place to check one is where it is chosen: before the owner signs a mandate.
The agent's key can call one method, spend, and spend has no address field. A payee enters through the mandate the owner signs.
Name a payee, and this page answers allow, warn or block, with the reasons. Your browser reads public NEAR and Base nodes itself. No wallet, no sign-in, and the check calls no Probarion server route.
The payee
What this check is, and is not
- Read-only. Your browser reads from rpc.mainnet.fastnear.com (falling back to rpc.intea.rs) on mainnet, rpc.testnet.fastnear.com on testnet, FastNEAR's archival nodes (archival-rpc.mainnet.fastnear.com and archival-rpc.testnet.fastnear.com) and, for a Base payee on mainnet, mainnet.base.org. It calls no Probarion server route, and this page saves nothing.
- Advice for the owner. The contract does not read this check: it pays a mandate's own payee, and the owner can still sign a mandate for a payee this page blocks.
- A read that fails or times out is unknown, and an unknown is a warning. Without a vault, lookalikes and past payments are not checked, and that is a warning too. So the page does not answer allow on a read it could not make.
- The blocklist is a seed, not a reputation service: 2 testnet names and 0 on mainnet, from Probarion's own eval cases and test fixtures. Probarion does not hold them, and none has a report of wrongdoing.
- On Base the age signal is the nonce, which does not show an age. Base is read on mainnet and not on testnet (a testnet vault pays Base through a stub), and Solana payees are not read, so those signals are unknown.
- The code is unaudited. The rules and the reads are the same ones the CLI's payee check runs.
The code: the rules (core) (opens in a new tab), the reads (SDK) (opens in a new tab), the seed blocklist (opens in a new tab), this page (opens in a new tab), report a payee (opens in a new tab).