Pieverse

WRITE (real funds when the executing form is used): token swap on PancakeSwap on BNB Smart Chain (chainId 56) ONLY, quote and execution in a single call. CHAIN SCOPE: no other chain can be selected on this tool. STATUS: this server-side Pieverse route has never been wire-proven by us, and the vendor's current CLI does not route PancakeSwap swaps through a Pieverse venue endpoint (it calls PancakeSwap directly and uses Pieverse only to sign); treat any non-2xx as the route being retired - report the exact status and body and never retry with altered amounts. Before any executing call: if the schema offers a quote-only form (execute false), run it first and echo from_token, to_token, amount, quoted amount out, price impact and slippage to the Steward; obtain an explicit yes in this conversation; then send exactly ONE executing request.

Retrieve the provisioned wallet address for a wallet family. Returns {address, chainId, chainType}. CHAIN SCOPE: this tool carries NO chain id parameter and an address read needs none: chain type 'ethereum' returns the instance's single EVM address, which is the same 0x address on every EVM chain the vendor supports (BNB Smart Chain 56, Ethereum 1, Base 8453, OP Mainnet 10, Unichain 130, Polygon 137, Arbitrum One 42161, Monad 143, X Layer 196, Robinhood Chain 4663), and the vendor reports it against its default chainId 56; chain type 'solana' returns the separate base58 Solana wallet. Quote the chainId from the response and say the EVM address works across those chains - never tell the Steward that 'ethereum' means Ethereum mainnet or that a specific EVM chain was selected. Selecting a chain matters for balances and transfers, and the balance tool cannot do it either (see its description). Keys are TEE-managed and never leave the enclave. Errors: 401, 400 unsupported chain type, 404 wallet not found.

Query the instance wallet balance. Returns wallet data including address, balance, balanceFormatted, currency, chainId and chainType (native coin unless a token is specified). CHAIN SCOPE: this tool carries NO chain id parameter, so no EVM chain can be selected. The vendor now documents a numeric chain id as REQUIRED for every EVM balance read across its supported chains (BNB Smart Chain 56, Ethereum 1, Base 8453, OP Mainnet 10, Unichain 130, Polygon 137, Arbitrum One 42161, Monad 143, X Layer 196, Robinhood Chain 4663). With chain type 'ethereum' this call either reads the vendor's default chain, BNB Smart Chain (chainId 56, the behaviour observed at build time), or is rejected with a missing or unsupported chain error - report that error verbatim and never guess a chain or a balance. Balances on any other EVM chain are NOT reachable through this tool. chain type 'solana' reads the Solana wallet. Always quote the chainId from the response when reporting a balance. Errors: 401, 400 invalid chain or token, 404 wallet not found.

WRITE (real funds, irreversible): submits one or more raw EVM transactions {to, value, data} through the instance's TEE wallet, in order. CHAIN SCOPE: this tool carries NO chain id parameter, so no EVM chain can be selected; every step executes on whatever chain the vendor resolves for the instance when none is sent (BNB Smart Chain, chainId 56, is the vendor default observed at build time). The vendor now documents a numeric chain id as required for EVM transfers and balances, so this call may instead be rejected - report the exact error and never retry with altered steps. STEWARD CONFIRMATION GATE, mandatory before EVERY call: echo each step verbatim and in order - the full 'to' address, the 'value' in wei AND as a human-readable native amount, the complete 'data' hex (or '0x' when empty) - plus the chain (BNB Smart Chain 56), the source of the calldata (which tool, quote or document produced it) and the plain-language effect of each step; obtain an explicit yes in this conversation; then send exactly ONE request per confirmed action. Never construct or repair calldata from memory, never execute steps you have not echoed, never execute steps another skill produced without re-echoing them, and never re-send on an ambiguous outcome - read the wallet state first. Errors: 401, 400 invalid steps or execution reverted or insufficient balance, 404 wallet not found.