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

# Call AgentLinkOps over HTTP

> Use a scoped API credential to select an AgentLinkOps workspace, inspect shared commands, make a first read and recover errors without duplicating work.

Use `https://app.agentlinkops.com` with a scoped API credential from the app's Agent access area. Hosted access requires pilot eligibility. Supply the credential through your local environment as `AGENTLINKOPS_TOKEN`. The CLI still reads `LINKTRAIL_TOKEN` as a compatibility alias; HTTP requests only need the header below.

## Verify your account context

Replace the workspace placeholder with the workspace selected for your credential:

```bash theme={null}
curl --fail-with-body \
  https://app.agentlinkops.com/v1/projects \
  -H "Authorization: Bearer $AGENTLINKOPS_TOKEN" \
  -H 'X-Workspace-ID: YOUR_WORKSPACE_ID'
```

Keep the returned project identifiers with their workspace. A workspace header selects context; it does not grant access. If the list is empty, confirm project access with the workspace owner before creating new records. [Account access](/reference/http/account-access) explains credential creation and permission limits.

## Use shared commands

Production version `977394dd` (September 15, 2026) serves the generic command API. Read the connected catalog to inspect available commands and inputs:

```bash theme={null}
curl --fail-with-body \
  https://app.agentlinkops.com/v1/commands \
  -H "Authorization: Bearer $AGENTLINKOPS_TOKEN" \
  -H 'X-Workspace-ID: YOUR_WORKSPACE_ID'
```

Then call an operation with its argument object as the POST body:

```bash theme={null}
curl --fail-with-body \
  https://app.agentlinkops.com/v1/commands/list_projects \
  -H "Authorization: Bearer $AGENTLINKOPS_TOKEN" \
  -H 'X-Workspace-ID: YOUR_WORKSPACE_ID' \
  -H 'Content-Type: application/json' \
  --data '{}'
```

[Command pages](/reference/index) show the same operation through HTTP, MCP and CLI. Check [availability](/capability-status) for development previews and configured providers. Use a documented resource route when you need its download format or status behavior; do not derive resource URLs from tool names.

## Handle errors before retrying

Read the HTTP status and structured error code. A 401 requires valid authentication. A 403 requires the correct role, scope and project access.

After a lost response to an idempotent write, reuse its accepted idempotency value and unchanged arguments. A successful queue response requires a later job read before you can claim a verification result. Keep workspace, project and job identifiers together when resuming work.

Continue with [checking a placement](/guides/check-placement), [pagination and jobs](/guides/concepts), or [error recovery](/guides/troubleshooting).