refactor: update API endpoints and documentation for new structure

[iamnivekx]

• Changed DefaultAPIURL to point to the new swap version endpoint.
• Updated various API paths to remove the versioning from the URL.
• Revised comments and documentation links to reflect the new API structure and provide clearer references.

[iamnivekx]

Switched to the new Jupiter swap API format used by providers like QuickNode

curl -s -L -g 'https://jupiter-swap-api.quiknode.pro/{your_key}/quote?inputMint=So11111111111111111111111111111111111111112&outputMint=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v&amount=100000000&slippageBps=50&restrictIntermediateTokens=true'

Removed /v1/ versioning from paths to follow their current unversioned API structure.
This aligns with how public integrations are now expected to consume the endpoint and reduces risk of path mismatch.

[ilkamo]

thanks for your contribution @iamnivekx

[iamnivekx]

I was wondering—do you think it might make more sense to submit a PR directly to the official jupiter-quote-api-node repository regarding the field format unification? That way, we could benefit from more stable updates and stay better aligned with upstream changes from the Jupiter team.

This way, we’d just need to sync the Swagger spec and regenerate the code each time, which would make maintenance much easier.

[ilkamo]

I was wondering—do you think it might make more sense to submit a PR directly to the official jupiter-quote-api-node repository regarding the field format unification? That way, we could benefit from more stable updates and stay better aligned with upstream changes from the Jupiter team.

This way, we’d just need to sync the Swagger spec and regenerate the code each time, which would make maintenance much easier.

That's a great idea, @iamnivekx! Do you have time to prepare the PR, or would you like me to take care of it?

[iamnivekx]

@ilkamo prepared the jup-ag/jupiter-quote-api-node#66

[ilkamo]

@ilkamo prepared the jup-ag/jupiter-quote-api-node#66

@iamnivekx I’ve added a comment with additional context under your PR and tagged the team for visibility. Let’s see how they respond.