Merge pull request #260 from 0xProject/solana-spec-sync

Author: D-J-Harris

fern/docs.yml

@@ -10,6 +10,9 @@ ai-search:
   location:
     - docs
 
+ai-examples:
+  enabled: false
+
 layout:
   searchbar-placement: header
   page-width: full

fern/docs/pages/api-reference-overview.mdx

@@ -22,7 +22,7 @@ Endpoints for EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, and more
 
 Endpoints for Solana (SVM):
 
-- **[Swap Instructions](/api-reference/solana-swap-ap-is/solana-swap/solana-swap-swap-instructions)**: Generate swap instructions for Solana tokens, returning versioned transaction data ready to sign and submit.
+- **[Swap Instructions](/api-reference/solana-swap-ap-is/swap/instructions)**: Generate swap instructions for Solana tokens, returning versioned transaction data ready to sign and submit.
 
 ## Cross-Chain API
 

fern/docs/pages/introduction/faq.mdx

@@ -595,7 +595,7 @@ https://api.0x.org/gasless/quote                          # Request a firm quote
 
     **For an integrator fee address:** No. You should assume the fee recipient ATA must already exist. If it may not exist, add a `createAssociatedTokenAccountIdempotent` instruction for the fee recipient + fee token mint yourself, **before** the swap/fee transfer path. See the [Integrator Byte Costs](/svm/solana-swap-api/guides/integrator-byte-costs) guide for how to account for the extra bytes this adds.
 
-    The relevant field is [`swap_fee_recipient`](/api-reference/solana-swap-ap-is/solana-swap/solana-swap-swap-instructions#swap_fee_recipient) — it accepts either a wallet address (for native SOL output) or a valid token account address (for token outputs).
+    The relevant field is [`swap_fee_recipient`](/api-reference/solana-swap-ap-is/swap/instructions#swap_fee_recipient) — it accepts either a wallet address (for native SOL output) or a valid token account address (for token outputs).
 
   </Accordion>
 </AccordionGroup>

fern/docs/pages/solana-swap-api/guides/get-started.mdx

@@ -16,7 +16,7 @@ Whether you're building a Solana-native experience or expanding an EVM-first pro
 
 ## Steps to Swap Token
 
-This guide will walk you through using the `/solana/swap-instructions` endpoint on 0x’s Solana API to:
+This guide will walk you through using the `/swap-instructions` endpoint on 0x’s Solana API to:
 
 1. Fetch a quote
 2. Build the swap instructions
@@ -26,7 +26,7 @@ This guide will walk you through using the `/solana/swap-instructions` endpoint
 
 Make sure you have:
 
-- [0x API key](https://docs.0x.org/docs/introduction/quickstart/getting-started)
+- [0x API key](/docs/introduction/quickstart/getting-started)
 - A funded Solana keypair (see details below)
 - A RPC Connection (see details below)
 
@@ -60,7 +60,7 @@ const connection = new Connection("https://api.mainnet-beta.solana.com");
 
 ## 1. Fetch a Quote
 
-Start by sending a POST request to the 0x `/solana/swap-instructions` endpoint to get swap instructions for a specific token pair and input amount.
+Start by sending a POST request to the 0x `/swap-instructions` endpoint to get swap instructions for a specific token pair and input amount.
 
 This endpoint returns everything needed to construct and execute a swap transaction.
 
@@ -87,11 +87,11 @@ const quote = await quoteResponse.json();
 
 ### Required Request Parameters
 
-For the complete list of required request parameters, see the [API Reference](https://docs.0x.org/api-reference/api-overview).
+For the complete list of required request parameters, see the [API Reference](/api-reference/api-overview).
 
 ### Example Response
 
-For a sample response, complete schema, and detailed field descriptions, see the [API Reference](https://docs.0x.org/api-reference/api-overview).
+For a sample response, complete schema, and detailed field descriptions, see the [API Reference](/api-reference/api-overview).
 
 ## 2. Build Swap Instructions
 
@@ -138,7 +138,7 @@ const instructions = buildInstructions(quote.instructions);
 
 ## 3. Resolve Address Lookup Tables
 
-Before you compile and sign a **v0 (VersionedTransaction)**, you need to resolve any **Address Lookup Tables (ALTs)** returned by the 0x `/solana/swap-instructions `endpoint.
+Before you compile and sign a **v0 (VersionedTransaction)**, you need to resolve any **Address Lookup Tables (ALTs)** returned by the 0x `/swap-instructions` endpoint.
 
 ALTs let Solana v0 transactions reference more accounts than can fit in the static account list by “looking up” additional addresses on-chain. If the quote response includes `address_lookup_tables`, you must:
 

fern/docs/pages/solana-swap-api/guides/important-integration-notes.mdx

@@ -24,7 +24,7 @@ We currently return **a single flat array of instructions.** Here's what’s cur
 - **Setup Instructions (N):**
   - These create associated token accounts (ATAs) for the user (`taker`) as needed. This uses `createIdempotent`, so instructions won’t fail if an ATA already exists.
   - The number of instructions (`N`) depends on how many tokens the route involves, sometimes there may be 1 extra instruction for native SOL support (for certain DEXs).
-  - **Integrator fee recipient ATAs are not created automatically.** The [`swap_fee_recipient`](/api-reference/solana-swap-ap-is/solana-swap/solana-swap-swap-instructions#swap_fee_recipient) field accepts either a wallet address (for native SOL output) or a valid token account address (for token outputs). If you're collecting fees on a token output, the token account you pass must already exist — 0x will not create it. If it may not exist, add a `createAssociatedTokenAccountIdempotent` instruction for the fee recipient + fee token mint **before** the swap/fee transfer path. See the [Integrator Byte Costs](/svm/solana-swap-api/guides/integrator-byte-costs) guide for how to account for those extra bytes.
+  - **Integrator fee recipient ATAs are not created automatically.** The [`swap_fee_recipient`](/api-reference/solana-swap-ap-is/swap/instructions#swap_fee_recipient) field accepts either a wallet address (for native SOL output) or a valid token account address (for token outputs). If you're collecting fees on a token output, the token account you pass must already exist — 0x will not create it. If it may not exist, add a `createAssociatedTokenAccountIdempotent` instruction for the fee recipient + fee token mint **before** the swap/fee transfer path. See the [Integrator Byte Costs](/svm/solana-swap-api/guides/integrator-byte-costs) guide for how to account for those extra bytes.
 - **Swap Instruction (1):**
   - A single instruction on our [**Settler**](https://github.com/0xProject/0x-settler) program to perform the actual swap.
 - **Cleanup Instructions (as required):**