PROXYLANE DEVELOPER DOCUMENTATION

Put the right guide
into your workflow

Read integration guides and provider comparisons directly from your editor, agent or HTTP client.

Authentication and scope

The public content interface is free and read-only. It needs no API key, account or OAuth token. Its requests retrieve ProxyLane documents and source-linked comparisons. For proxy configuration and MCP product details, read the relevant guide and MCP access overview. Registration and preferences use the website account flow.

Make your first request

curl --fail https://proxylane.dev/llms.txt
curl --fail -H 'Accept: text/markdown' \
  https://proxylane.dev/blog/python-requests-proxy
curl --fail https://proxylane.dev/compare/bright-data-vs-oxylabs.md

Choose the amount of context

llms.txt gives an overview, task guidance and described starting links
llms-index.txt lists every public document
llms-full.txt contains the complete public corpus in one large file
agents.md explains task selection and the account workflow

Every public content page has a .md alternative; the homepage uses /index.md. Read a single relevant guide first. The full archive can exceed 2 MB and is optional.

Formats and errors

Canonical pages serve HTML or Markdown according to Accept, including quality values. Responses include Vary: Accept, a canonical link and links to the alternate format and llms.txt. Unsupported content types return 406. Missing documents return 404 with recovery links. Request application/json on an invalid route to receive a structured problem response with a status, code and resolution hint.

curl -i -H 'Accept: application/json' \
  https://proxylane.dev/api/unknown-document

Integrate from a schema

The OpenAPI 3.1 description lists the public reading operations, parameter values and response formats. The API catalog links this description to its documentation. Operations are GET requests with no writes, purchases, pagination or subscription state. Cache the documents you read and avoid repeatedly downloading the full archive. If an edge service returns 429 or 503, honor Retry-After when supplied and retry with backoff.