docs(drift): draft from internal source

[pedromcunha]

Drafted from an internal source repo, requested by @Frizellle.

This PR was auto-generated by the reusable-docs-draft-pr workflow from a Claude-drafted update in the source repo. It is opened as a draft — please review, edit as needed, and mark ready for review before merging.

Review checklist

• Content matches the behavior shipped in the source PR
• No internal-only details (service names, file paths, unreleased names, security internals) leaked into the draft
• Conforms to CLAUDE.md style rules
• Cross-references and internal links resolve
• Any Needs human input items from the source comment are addressed

---

Generated by reusable-docs-draft-pr.yml in relayprotocol/agents-config.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
unevenlabs	🟢 Ready	View Preview	Sep 2, 2026, 10:06 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[greptile-apps]

Confidence Score: 3/5

Not safe to merge until the quote example uses the documented API-key header and the new Route Racing guide is reachable from the Features navigation.

Findings

1.  Wrong API-key header ▶
2.  Missing Route Racing navigation ▶

Summary

• This change adds Route Racing documentation and an API changelog entry. Validation confirmed that the quote example sends the API key through a header that does not apply key-scoped Route Racing access, and that the new guide is not included in the Features sidebar.

_{Reviews (1) · Last reviewed commit: "docs(drift): draft from internal source"}

[greptile-apps]

Route Racing API key is sent through the wrong header

The example uses Authorization: Bearer ${API_KEY}, but Relay API keys are supplied through x-api-key. The quote endpoint accepts the copied request as an unauthenticated public quote, which masks the issue; however, it cannot identify the key whose Route Racing grant should be applied. Use "x-api-key": API_KEY so copied integrations can opt into the key-scoped feature.

Artifacts

Route Racing API-key header validation source

• Executable validation source posts the same route-racing quote payload with the copied Bearer header or the documented x-api-key header, using a non-secret invalid key; it provides the reproducible comparison.

Before response using the copied Authorization Bearer header

• Captured execution of the copied documentation request against Relay quote v2, which returned HTTP/1.1 200 OK as a public quote; the takeaway is that acceptance does not apply a per-key grant.

After response using the documented x-api-key header

• Captured execution of the same Relay quote v2 request with x-api-key, which returned HTTP/1.1 200 OK; the takeaway is that this is the documented channel for key-scoped behavior.

_{Ran code and verified through T-Rex}