MCP for agents, REST for scripts

Amdahl exposes the same workspace operations two ways. Use MCP for agent clients like Claude and Cursor; use the REST API, this page, for scripts, automation, and backend services. Both authenticate with the same kind of API key, sent the same way.

1. Get an API key

In the Amdahl app, open Settings, then Developer and create an API key. It looks like amdahl_sk_live_…. You see the full key once, so copy it somewhere safe. Treat it like a password. Anyone with the key can act as you.

2. Send it on every request

Put the key in an X-API-Key header. The REST surface lives under https://app.amdahl.co/api/platform/v1. Here is a request that asks Amdahl who you are:

curl https://app.amdahl.co/api/platform/v1/me \
  -H "X-API-Key: amdahl_sk_live_your_key_here"

You get back your account details:

{
  "email": "[email protected]",
  "first_name": "Ada",
  "last_name": "Lovelace"
}

See what your key can do

Every workspace operation hangs off the same base URL. Call /operations to get the catalog of everything your key is allowed to call, each with its input schema:

curl https://app.amdahl.co/api/platform/v1/operations \
  -H "X-API-Key: amdahl_sk_live_your_key_here" \
  -H "Accept: application/json"

A 401 means the key is wrong or revoked; anything else means you are connected.

Keeping your key safe

• Never put it in front-end code or commit it to a repo. Keep it in a server-side secret or environment variable.
• Lost it or leaked it? Delete the key in settings and create a new one. The old one stops working immediately.
• You can have more than one key, for example one per script, so you can revoke them independently.