feat(docs): filter the routes table with the directory API and rename fixed rates

[letstokenize]

The available routes table on Supported routes now filters with the route directory API and can never filter down to zero routes. Each selector only offers choices that still match a route, clears on its own, and Reset clears them all. The fee coverage column becomes Fixed rates, with a note on how to get access.

Changes

• Directory filters: Source, Destination, Funding, and Fixed rates read GET /v1/routes with the API's own filters: sourceChain + sourceToken, destinationChain + destinationToken, method, and subsidies. The table shows what the directory returns for that selection. loadRoutes takes these filters.
• Dynamic selectors: each selector lists only values that leave at least one route given the other selections. Without a funding method, fixed rates apply to either method, as in the API. If clearing the method would then leave nothing, fixed rates clear too. If the directory returns nothing anyway (it changed since load), the table reloads with no filters.
• Clearing: a Clear link beside each active selector, and Reset beside the route count.
• Fixed rates: the column is renamed, and it reflects the selected funding method. The footer reads "Fixed rates make 1:1 or 1:par execution available for stablecoin payments or asset conversion. Access from the Tempo API Console. Contact for eligibility."
• The page intro, and the table's Markdown export for agents, describe the filters and fixed rates.
• Quote proxy: a GET to /api/routes-quote now answers 405 with Allow: POST instead of falling through to a 500.

The old either-side "Network" selector is gone, since the directory has no matching filter. Source and Destination still name each asset's network.

Testing

• pnpm check:types, oxlint, Biome, and the Zyzz style policy pass.
• A production build passes, and so does pnpm check:markdown (277 pages).
• E2E: 27 pass, against a production build. The three new table tests mock the directory with the API's filter semantics. They check:
  • the filter query parameters sent
  • narrowed options
  • clearing each selector, and Reset
  • that clearing the funding method never leaves zero routes
  • the column name and footer links
• Checked by hand against the live directory (28 routes): choosing USDT · Tron as the destination requests destinationChain=tron:0x2b6653dc&destinationToken=…, shows 2 of 28 routes, and narrows Source to OUSD and USDT0 on Tempo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tempo-docs	Ready	Preview	Oct 11, 2026 7:15am UTC