Privy
Thirteen tools over the caller's own Privy user, wallets, wallet actions, and transactions.
The Privy category is the caller's own Privy account, and every tool in it is
scoped to them. It has four subcategories:
Users— read the current user, write the per-user custom metadata.Wallets— list, read, and read the balance of the caller's own wallets, and their transactions.Actions— the wallet-action queue for the caller's wallets. Read a whole list, or one action by id to check what happened to it.Transactions— read one transaction, poll for its status, and prepare a transaction for the user to sign in the browser.
The rule that shapes this category
These tools run under a Privy DID, not an sk- key. An sk- key names an
account; a wallet action needs a wallet, and the wallet belongs to a person. A
caller holding only a key gets a clear refusal rather than a call against
nobody's wallet.
prepare_transaction is a request, not a send
privy_prepare_transaction does not sign and does not broadcast. It produces a
wallet action the user signs in the browser, and returns something you can then
read back:
privy_get_wallet_action— one action by id, for a per-action status check. Use it to confirm a prepared transaction was actually picked up, or to read the per-stepstepsarray after a failure.privy_get_transaction_status— the poll loop for the transaction itself.privy_get_transaction— read one transaction directly.
The same two-step shape appears in the Onchain category's tx_request_status,
and the same in Social before a post goes out. Nothing here moves a value or
posts a message on the server's own initiative.
media_asset_list
List the assets you own, newest first, optionally filtered to one project or one stored file kind. Returns each asset's id, kind, status, credit cost, and — for completed assets — a short-lived signed URL into Putty's own storage. Use it to find an asset id for `media_edit_image`, `media_generate_video`, or `media_vectorize_logo`, to see what a marketing pack produced, or to check how much a project has spent on media. Only the caller's own assets are ever returned; a project id belonging to another user yields an empty list, and an asset id belonging to another user is a plain not-found in the tools that take one.
Users
The current user and the custom metadata attached to them.