fix(docs): explain Routes quote proxy failures instead of a bare HTTP status

[letstokenize]

Summary

When a reader quotes a route in the Routes tester without their own API key and the docs quote proxy fails, the tester showed "The request failed with HTTP 404." That reads like the Routes API rejected the request. It now says "The docs demo quote service is unavailable. Add your project API key to quote. (quote_proxy_unavailable)", which names the failing piece and the fix.

Changes

• The proxy relays Routes API errors unchanged as JSON. So a docs-key failure without a JSON error code, such as an HTML 404 or a plain-text 500 from the hosting layer, is now classified as quote_proxy_unavailable.
• Updated the quote_proxy_unavailable guide text to say the demo quote service is unavailable.

Testing

• Extended the docs-proxy fallback test with an HTML 404 from the proxy.
• vitest run src/lib/routes-execution.test.ts (17 passed), pnpm check:types, biome check.

Notes

• The production proxy is currently broken: GET https://tempo.xyz/developers/api/routes-quote?... returns a plain-text 500 Internal Server Error, and https://tempo.xyz/api/routes-quote redirects to an HTML 404. The handler only returns JSON, so the route is not being served by the deployment. This PR fixes the message, not the proxy.
• The API calls panel still shows the original api.tempo.xyz URL for the proxied attempt.

[vercel]

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

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