Get started

Authentication

Every request carries an API key. A key belongs to a workspace and spends that workspace's credits.

Create a key

Open Settings → API keys and create a key. It starts with rdx_ and is shown once, so copy it somewhere safe. You can make several keys, one per integration, and revoke any of them without touching the others.

Send the key

Put the key in the X-API-Key header. The REST API and the MCP server read it the same way.

X-API-Key header
curl https://api.rolodexy.ai/v1/credits \
  -H "X-API-Key: rdx_your_key"

Tools that only let you set a bearer token can send Authorization: Bearer rdx_your_key instead.

Bearer token
curl https://api.rolodexy.ai/v1/credits \
  -H "Authorization: Bearer rdx_your_key"

When a key is missing or wrong

The API answers 401 with the code unauthorized. The MCP server also sends a WWW-Authenticate: Bearer header so clients know to ask for a key.

401 response
{ "error": { "code": "unauthorized", "message": "Missing or invalid API key. Send it in the X-API-Key header." } }

Keeping keys safe

Rolodexy does not offer OAuth sign-in for apps yet. Assistants that can only connect through OAuth, such as the Claude and ChatGPT web apps, cannot use the MCP server today; see AI assistants for the ones that can.