cherry-pick: metadata-coverage Jupiter fix to main - #1400
Merged
Conversation
…kens/v2/search (#1399) 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See dev PR.