Palace Verify takes the verification engine behind Password Palace and exposes it as a plain API. A buyer mints a "room" once, anchored on the Memoria chain, and then verifies attempts against it as often as they need. There is no account, no wallet, and no OAuth flow for anyone involved: an API key and a room ID are the whole interface.
Why It Exists
AI agents increasingly need a human to confirm something: approve a payment, unlock a record, authorize an action. The usual answers (log in, OAuth consent, a one-time code over SMS) all assume an account system on both sides. Palace Verify inverts the OTP: the secret doesn't rotate, and the agent never sees it. It only learns pass or fail.
Key Features
- >No Account, No Wallet: An API key is issued on request; rooms are anonymous
- >Create / Verify / Revoke / Balance: Four calls cover the lifecycle. Rooms can carry a use limit and an expiry; revocation is immediate
- >On-Chain Anchor: Each room's commitment is minted on the Memoria chain through a relayer, so the buyer never touches gas or keys
- >Secret Entropy Floor: A static-secret adapter rejects weak secrets before a room is minted
- >Exactly-Once Credits: Credit purchases are recorded in a checkout ledger that grants each payment exactly once, even when the payment webhook retries
- >Agent-Native Design: Specced as an MCP tool surface, including a device-flow handoff where the agent asks a human to confirm at a link and polls for the result
Status
The core service and credit purchasing were built July–September 2026 and verified end to end on devnet (mints, a true and a false verification, credit accounting). The public endpoint is not currently answering, so this is listed as beta until it's back up.
Tech Stack
TypeScript / Express routes in the Password Palace custodial backend, PostgreSQL for credit accounts and anonymous rooms, CosmWasm contract v4.3.0 on Memoria for on-chain anchoring.