codex-gateway

To handle a 402 Payment Required response when querying a GraphQL API, you can use an MPP 402 challenge flow to pay per query. This approach automatically manages payment credentials without needing a standard API key.

The MPP 402 challenge flow for GraphQL queries is a payment mechanism that processes per-query payments. It intercepts 402 Payment Required responses and uses messaging protocol credentials to authenticate and unlock the requested data.

You do not need an API key to query the Codex Supergraph if you use the MPP 402 challenge flow. Instead of static API keys, this method facilitates continued queries by handling payment credentials dynamically on a per-query basis.

To query the Codex Supergraph on a per-query payment basis, execute your GraphQL query and let the MPP flow manage the 402 Payment Required response. It automatically interacts with payment credentials to authorize each request.

Handling GraphQL 402 payment challenges does require client-side support for the MPP flow. Your environment must also include messaging protocol dependencies and GraphQL knowledge to process the per-query credentials correctly.

A GraphQL query returns a 402 Payment Required status on the Codex Supergraph when the requested data demands payment for access. Triggering the MPP 402 challenge flow resolves this by providing the necessary transaction credentials.