> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/reader-guides.md). # Reader Guides - [Getting Started Guides](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy.md): Build your first HTTP proxy route and confirm that the gateway rewrites and forwards traffic correctly. This guide covers defining a server alias, creating a - [Quickstart: Health Endpoint](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-health-endpoint.md): Ship a minimal health endpoint before you add upstream integrations so deploys are observable from day one. The config returns a static JSON response with no - [Quickstart: JWT-Protected Route](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-jwt-protected-route.md): Protect a single route with HS256 JWT validation without forcing authentication on every endpoint. This guide shows how to add an authorizer block and flag - [Quickstart: Auth0-Protected Route](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-auth0-route.md): Stand up an Auth0-backed route when you need hosted identity and token validation at the edge. This guide covers the authorizer block for Auth0, the callback - [Quickstart: Supabase Passwordless API](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-supabase-passwordless.md): Use Supabase OTP flows when your product needs passwordless auth routes behind one Worker gateway. This guide covers both the auth request and verify endpoints. - [Quickstart: Inline Config with SAG\_API\_CONFIG\_JSON](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-inline-config.md): Use inline config for demos, tests, and disposable environments where a separate config file is unnecessary. The entire gateway definition lives in a single - [Quickstart: KV-Backed Config](https://docs.serverlessapigateway.com/reader-guides/quickstart-first-proxy/quickstart-kv-config.md): Move config into Cloudflare KV when you want the gateway to load its routing definition at runtime. This decouples config updates from worker deploys, so you - [Routing](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard.md): Use this page to choose the right route shape and avoid accidental matches when multiple patterns overlap. The gateway evaluates exact paths first, then - [Routing: ANY Method](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-any-method.md): Use ANY when the backend accepts the same behavior for multiple verbs and you want one config entry. This reduces duplication when a single upstream endpoint - [Routing: Explicit OPTIONS Handlers](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-explicit-options-handlers.md): Add explicit OPTIONS routes when a path needs custom preflight behavior instead of the default CORS 204 response. By default, the gateway handles OPTIONS - [Routing: Prefix Add and Remove](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-prefix-add-remove.md): Map public paths to upstream paths cleanly when the origin and public API use different prefixes. The gateway can strip a prefix from the incoming path before - [Routing: Multiple Upstreams Behind One Domain](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-multi-upstream-patterns.md): Split one public API domain across several backends while keeping routing rules readable. Define multiple server aliases in the \`servers\` array and reference - [Routing: Static Response Routes](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-static-response-routes.md): Return fixed JSON or simple values directly from config for health checks and low-risk utility endpoints. Static response routes bypass integration entirely, so - [Routing: Match Priority Explained](https://docs.serverlessapigateway.com/reader-guides/routing-exact-vs-parameter-vs-wildcard/routing-path-priority-explained.md): Understand why exact matches beat parameterized routes and why parameterized routes beat wildcard routes. The gateway evaluates all defined paths against the --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/reader-guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.