Jupiter Integration Readiness
jupiter-integration-readiness-2026-06-29.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw fileJupiter Integration Readiness
Generated: 2026-06-29
This note records the Jupiter-facing compatibility work for the current PDAO community token on Solana Mainnet.
PDAO Token Surface
- Current Mainnet community token:
9isGuumtaqvJeJeyLF44fvfskk2cv5mYsopexMBfpump - Token page:
https://privatedao.org/token/ - Token metadata:
https://privatedao.org/token.json - Pair:
EZiPEFFGhvU7BmZTcsJxKFVw7Edby7KxN91fGfzpxHpz - Jupiter swap route:
https://jup.ag/swap/SOL-9isGuumtaqvJeJeyLF44fvfskk2cv5mYsopexMBfpump
Jupiter Plugin
PrivateDAO uses Jupiter Plugin for the token page swap surface instead of the deprecated Terminal toolkit.
- Docs:
https://dev.jup.ag/docs/tool-kits/plugin - Mode:
integrated - Powered by: Ultra
- Initial input mint: SOL
- Initial output mint: PDAO
- Fixed mint: PDAO
- Project RPC requirement for this widget: none
Express Verification
Jupiter Express Verification is prepared but not submitted in this repository state.
- Docs:
https://dev.jup.ag/docs/tokens/verification - API reference:
https://dev.jup.ag/docs/api-reference/tokens/verify-check-eligibility - VRFD X account:
https://x.com/jup_VRFD - Payment/signing boundary: Express Verification requires a signed payment
transaction and burns 1000 JUP.
- Free verification surface:
https://verified.jup.ag
The prepared CLI path is:
scripts/submit-pdao-jupiter-vrfd.sh --dry-runscripts/submit-pdao-jupiter-vrfd.sh
The script does not print wallet private keys, API keys, keypair paths, or secret material.
Developer Platform Migration
Jupiter Portal has migrated to the Developer Platform.
- Dashboard:
https://developers.jup.ag - Migration guide:
https://developers.jup.ag/docs/portal/migration - API base URL remains:
https://api.jup.ag - Lite API availability boundary:
https://lite-api.jup.ag - Billing grace period noted by the announcement:
2026-06-30
Operational note: API keys should be kept in environment/secret storage only. Newly created keys should be saved at creation time because fully viewing them later is not part of the new platform flow.
Deprecated Jupiter Surfaces Avoided
The token page and metadata avoid the following deprecated surfaces:
- Old Terminal toolkit
- Beta Content API:
/tokens/v2/content/content/feed/content/cooking- Pre-v7 Metis binary
Metis binary references:
- Releases:
https://github.com/jup-ag/metis-binary/releases - Binary key portal:
https://portal.metis.builders
Prediction Markets API Compatibility
PrivateDAO's PDAO token page does not use Jupiter Prediction Markets order placement, but the project records the compatibility rule because the TxLINE product touches prediction-market settlement.
Post-breaking-change market item fields must be read from the top level:
markets[].titlemarkets[].isTeamMarketmarkets[].rulesPrimarymarkets[].rulesSecondarymarkets[].openTimemarkets[].closeTime
Do not use:
markets[].metadata.titlemarkets[].metadata.isTeamMarketmarkets[].metadata.rulesPrimarymarkets[].metadata.rulesSecondarymarkets[].metadata.openTimemarkets[].metadata.closeTime
Minimum order size for Jupiter Prediction Markets orders should be at least 5 USD.
Discovery Links
The machine-readable token metadata now includes discovery links for Jupiter, Pump.fun, DexScreener, GeckoTerminal, Birdeye, Solscan, Solana Explorer, SolanaFM, RugCheck, DexTools, GMGN, Streamflow, GitHub, Colosseum, Superteam, X, Telegram, and Discord.