> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nodemaven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proxy capabilities

> Discover which configuration options are valid for a product before you build a proxy string, instead of hardcoding them.

The proxy capabilities endpoint tells you which configuration options are valid for a product. The point of calling it is to discover the valid configuration surface at runtime rather than hardcoding a list of options that may change.

All requests go to `https://api.nodemaven.com/api/v2/base/` and carry the header `Authorization: x-api-key YOUR_API_KEY`. See the [NodeMaven API overview](/proxy-api/overview) for the shared basics.

## Endpoint

| Method | Path | What it does | Responses |
| - | - | - | - |
| `GET` | `/proxy-capabilities/` | Discover the valid configuration surface for a product | 200, 422 |

```bash theme={null}
curl https://api.nodemaven.com/api/v2/base/proxy-capabilities/ \
  -H "Authorization: x-api-key YOUR_API_KEY"
```

Call this before you assemble a proxy string, and build the string from what comes back. That way a configuration option you did not know about, or one that is not valid for the product you are using, does not turn into a failed connection you have to debug.

`GET /proxy-capabilities/` can return 422. Read the response body for the reason.

## Related reading

* [Proxy string](/residential-mobile/proxy-string) explains how the configuration options you discover here are expressed in a username.
* [IP filter modes](/residential-mobile/ip-filter-modes) covers one of the configuration choices in detail.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.