Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.myproceeds.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Custom headers and query parameters live on the paywall, not the service. Use them when one specific endpoint needs additional context that the rest of the service doesn’t.

​
Custom headers

Add a header name and value on the paywall. Proceeds attaches the header to every proxied request before forwarding it to the upstream Target URL. Common uses:
  • Pinning an upstream API version: Accept-Version: 2026-04-01
  • Identifying the calling product to a multi-tenant upstream: X-Tenant: weather
  • Triggering upstream feature flags

​
Query parameters

Add a parameter name and value on the paywall. Proceeds appends the parameter to the upstream URL. Common uses:
  • Pinning a model name on an inference API: model=claude-opus-4-7
  • Forcing a specific data source: source=premium
  • Locking a region: region=us-east-1

​
Layering

Headers and params stack on top of upstream auth and the client’s own request:
  1. Proceeds attaches upstream auth (configured at the service level).
  2. Proceeds attaches paywall custom headers and query parameters.
  3. The client’s request body and additional query parameters pass through unchanged.
If the same header name appears on both the paywall and the client request, the client value wins for non-auth headers. Auth headers configured via Forward upstream auth always win — they can’t be overridden by the client.
Use custom headers to pin sensitive defaults that you don’t want clients to override, like an API version or a tenant ID.