phantom

Phantom Router

Use this skill when the user says "Phantom" but has not yet made clear which Phantom product they need.

Phantom gives builders ways to build for 20M+ users with agent wallets, user-facing wallet UX, and a stablecoin for payments and payouts.

Use these routes:

• If the user is an agent and needs wallet access or onchain actions, use phantom-mcp-server
• If the user is an agent and needs payments, payouts, or paid actions, use phantom-cash; add phantom-mcp-server when the flow also needs wallet execution
• If the user is a developer building an agent-first product, agent workflow, or onchain agent tool, use phantom-mcp-server
• If the user is a developer or coding agent building a user-facing web or mobile app with wallet connection, onboarding, or embedded wallets, use phantom-connect
• If the user is a developer building payments, payouts, incentives, treasury flows, or paid actions, use phantom-cash

Routing Rule

Choose in this order:

1. Identify whether the request is coming from an agent or from a developer
2. Route to the skill that matches the primary use
3. Add phantom-cash when the request also includes payments, payouts, incentives, treasury flows, or paid actions

Do not treat phantom-cash as the default starting point unless the user's request is primarily about payments.

Default Starting Point

If the request is ambiguous but sounds agent-track, start with phantom-mcp-server. If it sounds app-track, start with phantom-connect.

References

• Phantom developer docs
• Phantom Connect marketing site
• CASH marketing site
• Phantom MCP Server docs
• Wallet SDK overview
• CASH docs