Read the current Pi and custom-token balances of a Pi wallet address. Call this whenever you need to know how much Pi an address holds, whether it holds a particular token, or whether the account exists on-chain at all. Reads public ledger data only — it cannot move funds and needs no credentials. An address that has never been funded on this chain is not an account there: the call returns a not-found error rather than a zero balance, so 'absent' and 'holds nothing' stay distinguishable. This server reads Pi Testnet, and every result repeats that in its "network" field — always report which chain a figure came from. Pi Mainnet and Pi Testnet are separate ledgers sharing one address format, and the same address can hold different balances on each, so a result from the wrong chain looks entirely normal. Testnet Pi has no monetary value: never present a testnet balance as real holdings.

List payments sent to or from a Pi wallet address, newest first. Call this to answer questions about an address's transaction history — whether a payment arrived, who funded an account, or what it recently sent. Covers payments, account creations, path payments, and account merges. Results are paginated: pass the returned next_cursor back as cursor for the next page. Reads public ledger data only. An address never funded on this chain returns a not-found error rather than an empty list, so an empty payments array means you have paged past the end of the history — not that the account is unused. This server reads Pi Testnet, and every result repeats that in its "network" field — always report which chain a figure came from. Pi Mainnet and Pi Testnet are separate ledgers sharing one address format, and the same address can hold different balances on each, so a result from the wrong chain looks entirely normal. Testnet Pi has no monetary value: never present a testnet balance as real holdings.

Look up a single Pi transaction by its hash and report whether it succeeded, which ledger it landed in, who submitted it, the fee charged, and its memo. Call this to verify that a specific transaction actually went through — a user or another service claiming a payment was made is not proof; this is. Reads public ledger data only. A hash this chain has no record of returns a not-found error, which is not the same answer as successful: false — that means the transaction did reach a ledger and was rejected there. This server reads Pi Testnet, and every result repeats that in its "network" field — always report which chain a figure came from. Pi Mainnet and Pi Testnet are separate ledgers sharing one address format, and the same address can hold different balances on each, so a result from the wrong chain looks entirely normal. Testnet Pi has no monetary value: never present a testnet balance as real holdings.

Check whether a Pi user access token is genuine and, if so, who it belongs to. Call this to authenticate someone who claims a Pi identity — never trust a client-supplied uid or username on its own; this is the only thing that proves it. An invalid, expired, or wrong-app token returns valid: false with a reason rather than failing; only a transport or server fault is reported as an error. Sends the token to the Pi Platform API (https://api.minepi.com/v2/me) and nothing else; it is not stored or logged. Note the uid is app-specific — the same person has a different uid under a different Pi app. Unlike this server's ledger reads, this is an identity check against the Platform API rather than a chain query, so the result carries no network field and does not depend on which Pi chain is being read.