Read account verification state

Whether this account can use the merchant tools (checkouts and products), and exactly what is missing if it cannot. Send a Bearer JWT or an sk_ API key; NO scope is required. Read-only. Two proofs exist and method says which one applies. A human account proves ownership of a bank account: receive at least requirements.deposit_cents from one CPF/CNPJ and withdraw at least requirements.withdraw_cents back to the SAME document, both inside one window of requirements.max_days_between_legs days, and with the account at least requirements.min_account_age_days old (0 today — no waiting period). The withdrawal is measured in DePix LEAVING the wallet — the amount you enter — not in what lands in the bank, so it is a number you control. An agent account proves a domain instead (POST /api/agents/verify-domain). steps is the checklist in the order it must be done, including converting a little DePix to L-BTC to pay the Liquid network fee — without it a withdrawal cannot be broadcast at all. Render steps as given. Only movements made after this feature went live count — older history never verifies an account by itself. Verification is INDEPENDENT of how much the account may receive: it unlocks tools, never a limit. Poll this while the customer completes the steps, then call POST /api/verification.