Skip to content

hotfix(metadata-coverage): Jupiter probe switch to new API - #1399

Merged
Flotapponnier merged 1 commit into
devfrom
hotfix/metadata-jupiter-v2
Jul 24, 2026
Merged

hotfix(metadata-coverage): Jupiter probe switch to new API#1399
Flotapponnier merged 1 commit into
devfrom
hotfix/metadata-jupiter-v2

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

See commit.

…kens/v2/search

Jupiter migrated jup.ag off Next.js; HTML scrape of __NEXT_DATA__ started
returning next_data_not_found on every call, dropping Jupiter's coverage
rate to 0% on the bench.

Replace scrape with the JSON endpoint the Jupiter web app now uses.
Keyless, rate-limited per IP. Jupiter's swap-focused model doesn't
carry description/socials, so those stay false by design (~25% floor).
@Flotapponnier
Flotapponnier merged commit d524dc9 into dev Jul 24, 2026
1 check failed
@Flotapponnier
Flotapponnier deleted the hotfix/metadata-jupiter-v2 branch July 24, 2026 20:20
Flotapponnier added a commit that referenced this pull request Jul 24, 2026
…kens/v2/search (#1399) (#1400)

Jupiter migrated jup.ag off Next.js; HTML scrape of __NEXT_DATA__ started
returning next_data_not_found on every call, dropping Jupiter's coverage
rate to 0% on the bench.

Replace scrape with the JSON endpoint the Jupiter web app now uses.
Keyless, rate-limited per IP. Jupiter's swap-focused model doesn't
carry description/socials, so those stay false by design (~25% floor).

Co-authored-by: Florent Tapponnier <contact@mobula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant