Skip to main content
Everything in this section exists for one reason: a language model reading a documentation site built for humans wastes tokens on navigation, and often reads the wrong thing. So we publish the same content in three shapes a model can consume directly. All three are free, need no key, and are read-only.

LLM References

Two text files with the whole portal in them, following the llms.txt standard.

Docs MCP Server

Live search over this documentation, for MCP-capable clients.

​
Which one fits your setup

That last one is worth knowing on its own:
Same page, no navigation, no HTML.

​
Not to be confused with the MCP Server

There are two MCP servers in this documentation and they do completely different things. If you want an agent that does things - provisions proxies, sets limits, reads your balance - you want the MCP Server. This section is about an agent that knows things.

​
Using both together

They complement each other well. A coding assistant with the documentation loaded writes correct usernames and picks the right session parameters on the first attempt, because it knows the format. The same assistant connected to the MCP server can then create the proxy it just wrote code for.
If you only do one thing: point your coding assistant at llms-full.txt before you start building the integration. Most of the time people lose to proxy integration is spent on the username parameter format, which is all in there.

​
Next steps

LLM References

The two files, what is in each, and how to load them.

Docs MCP Server

Connect a client to live documentation search.