integrating-jupiter
Comprehensive guidance for integrating Jupiter APIs (Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing). Use for endpoint selection, integration flows, error handling, and production hardening.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./vendored/jupiter/integrating-jupiter/SKILL.mdThe canonical home for this skill is integrating-jupiter in jup-ag/agent-skills
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill provides integration flows and operational code to execute token swaps, lending deposits, limit orders, recurring purchases, and token transfers via Jupiter APIs (e.g., POST `/swap/v2/execute`, POST `/lend/v1/earn/deposit`, POST `/send/v1/craft-send`), constituting direct financial operations (token swaps, purchases, transfers). These financial operations rely entirely on client-side private key signatures and API keys without independent service-side authentication or authorization checks that independently validate and authorize the financial transaction execution; therefore, direct operations lack established qualifying independent access control.
- Repository
internet-court/internet-court-skill
- Revision
fa89195
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.