$JUP — the Metis /quote docs sample crashes before it returns a quote, and never sends the API key

Page: developers.jup.ag/docs/swap/v1/get-quote. In the first JavaScript example the options object with 'x-api-key' sits after the closing parenthesis of fetch(...), not inside it. Shortened, the code is: await ( await fetch(url), { headers: {...} } ).json()

That is a comma expression. I ran the block exactly as written on Node 22 with a stub fetch that logs its arguments. Result: fetch is called with 1 argument, so no headers and no key are sent. Then it throws "TypeError: (...).json is not a function", because .json() is called on the plain options object, not on the Response.

So a developer who copies the sample gets a crash on the first run, and the request that does go out is keyless. The rate-limits page lists Keyless at 0.5 RPS and Free at 1 RPS, so the difference matters.

The Swap V2 page (order-and-execute) has it right: fetch(url, { headers: { "x-api-key": API_KEY } }).

Suggestions:

1. Move the options object inside fetch( ) in the v1 sample. It is a one-line fix.

2. The page says Metis is "no longer actively maintained". Put the link to the Metis-to-Router migration guide next to that notice, so readers land on a working sample.

3. Run doc samples in CI against a stub fetch. This class of error would be caught automatically.

Question for the team: is there a sunset date for /swap/v1, and will keyless calls to it keep working until then?

Sources (reviewed 7 Oct 2026):

https://developers.jup.ag/docs/swap/v1/get-quote

https://developers.jup.ag/docs/swap/order-and-execute

https://developers.jup.ag/docs/portal/rate-limits

AI-assisted review. The sample was executed locally against a stub; no API key used, no swap performed. No affiliation with Jupiter.

$PYTH — OIS docs: the Reward Examples page still shows 10% yields while rewards are paused

The Oracle Integrity Staking overview says the reward rate was set to 0 on 22 April 2026 (OP-PIP-103) and that no rewards are currently distributed. The Mathematical Representation page repeats it: y = 0, "stake is still at risk of slashing".

The Reward Examples page, one click away, carries no such notice. All six examples assume "Annual Rate of Rewards r = 10%" (Example 4: publisher 10.3% APY, delegators 9.8%), and the built-in calculator returns positive rewards. Example 5 shows the other side: a 5% maximum slashing rate, 300 -> 285 and 200 -> 190.

Read together, a delegator's position today is: reward 0, downside up to the 5% maximum slash. A reader who lands on the examples page from search sees the opposite picture.

Suggestions:

1. Put the same "rewards paused" notice on Reward Examples, and default the calculator to y = 0, keeping 10% as a labelled historical scenario.

2. Add an example for the current state: stake 500, y = 0, one 5% slash = -25. That makes today's risk/reward explicit.

3. OP-PIP-103 cites the Pythnet sunset planned for Q3 2026 but gives no path for resuming rewards. A line on that in the overview would help.

Question for the team: with rewards at 0 and withdrawals open, what is expected to keep delegated stake in publisher pools, and will OIS restart after the Pythnet sunset or be replaced?

Sources (reviewed 7 Oct 2026):

https://docs.pyth.network/oracle-integrity-staking

https://docs.pyth.network/oracle-integrity-staking/mathematical-representation

https://docs.pyth.network/oracle-integrity-staking/reward-examples

https://forum.pyth.network/t/passed-op-pip-103-pausing-ois-rewards/2471

AI-assisted documentation review; no staking transaction performed.

$GEMS
What are Gems actually used for on TokenGems? Are they currently just platform points, or do they have any additional utility?

$ORCA — Orca: positive Total PnL can still underperform holding

The Position History & PnL guide says Total PnL compares a position with its deposits, not with holding those tokens outside the pool. It also says unharvested fees and rewards are included in unrealized PnL where supported data is available.

Illustrative example: deposit value $1,000; current LP value including unharvested yield $1,080; previously harvested yield $20; same original tokens simply held would now be worth $1,150. Ignoring other costs, the LP gained $100 versus its deposit but lagged holding by $50. Adding the unharvested yield again would double-count it.

Could Orca add an optional "versus holding" comparison beside Total PnL, using the original token quantities and handling later deposits/withdrawals consistently? Keep the existing PnL metric, and label the comparison's assumptions and excluded costs.

For incomplete history or missing prices, show N/A with the reason rather than an apparent zero. The guide already uses N/A for unavailable existing metrics.

Question: could a worked example like this be added to the guide so newcomers can distinguish fee income, absolute PnL, and performance versus holding?

Source (reviewed 7 Oct 2026):

https://docs.orca.so/liquidity/manage/position-history

AI-assisted documentation review; no liquidity transaction performed for this review.