sap_phoenix_build_onboard_trader

ai.oobeprotocol.sap.mcp/sap-mcp · Verify this server

Build Phoenix trader ACTIVATION instructions (enables all six capabilities incl. deposit). ALWAYS required after register — a RegisterTrader-only account is frozen and every deposit simulates CapabilityDenied. Fetches instructions from Phoenix's build-register-ixs API (the only source of the OnboardTraderDelegated instruction). The browser assembles and signs them, then MUST submit via sap_phoenix_submit_onboard_trader — never via plain RPC, the onboarder signature exists only inside Phoenix's send-register-ixs. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.