We audited the Jupiter developer documentation in May 2026 and found 21 issues. We checked the same pages again on 11 October 2026. After our copy of 28 May, Jupiter changed the text behind six of the 21: five fixed and one partly fixed. This page lists each change, with its date and how it compares with what we recommended. It shows that these findings pointed at text Jupiter later changed. It does not show why Jupiter changed it, and it does not show that the other findings are wrong. We do not claim our audit caused any change. The full audit is here; the comparison for all 21 is on the re-audit page.
The six changed findings
| Finding | First rating | What we found | What the docs show now | When | Compared with our recommendation |
|---|---|---|---|---|---|
| F-1 | Critical | Every page sent readers and crawlers to the old documentation host, and so did the sitemap. | Banner and sitemap now use developers.jup.ag. | not later than 2026-10-02 (archived copy of swap.md shows the new host); not earlier than 2026-05-28 (our mirror) | Mostly applied |
| F-2 | Critical | Seven Ultra endpoints were billable in the pricing table, with no reference pages. | Ultra rows are gone from the pricing table; the Ultra pages now say the API is superseded by Swap V2. | not later than 2026-06-22 (commit 4af7be640 in Jupiter public docs repository removed the rows); not earlier than 2026-06-15 (archived copy still lists them) | Partly as recommended |
| F-8 | Medium | One API spec named a third portal hostname. | All specs use the same portal address. | not later than 2026-06-08 (commit 3ba0297 in Jupiter public docs repository changed the one line); not earlier than 2026-05-28 (our mirror shows the old wording) | Applied as recommended |
| F-10 | Medium | The transaction endpoint was the only API on the tx path prefix. | It moved to its own host, tx.jup.ag, and its docs page was rewritten around it. | not later than 2026-07-29 (commit 0fcca1c in Jupiter public docs repository); not earlier than 2026-05-28 (our mirror) | Different route |
| F-14 | Medium | The sitemap was rebuilt in May but still on the old host. | The sitemap is entirely on developers.jup.ag. | not later than 2026-10-11 (our fetch); not earlier than 2026-05-28 (our mirror) | Applied as recommended |
| F-15 | Medium | A breaking-change notice for 14 May still read as upcoming two weeks after. | It is now in past tense in the May changelog post. | not later than 2026-10-11 (our fetch); not earlier than 2026-05-28 (our mirror) | Applied in effect |
Where a date is a commit in Jupiter's public documentation repository (github.com/jup-ag/docs) it is the day of the change. Other changes lie between two dates, so those are bounds, not the day of the change: the banner host and the sitemap are hosting settings, and the changelog is not in that repository. The comparison with our recommendation is by text only; it does not show that Jupiter used our recommendation. What the docs show is as read on 11 October 2026.
The other 15 findings: 13 were unchanged when we checked on 11 October 2026; one (F-16, broken links) could not be judged because our May count came from a partial copy of the site; one (F-5, Trigger v1 and v2) cannot be placed after our audit, because Jupiter's public source already pointed that page at v2 on 27 March 2026 although our copy of the live page on 28 May still showed v1. Unchanged does not mean wrong. We also made mistakes: the count of API titles in F-3 and a supposed inconsistency in F-5 were corrected in our own revised report (V3) before this check. 6 + 13 + 1 + 1 = 21.