> ## 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

> Authenticate with a scoped API credential, select a workspace, and send requests using the shared command and resource endpoints.

The hosted API origin is `https://app.agentlinkops.com`. Use a scoped API credential created in the app's Agent access area. Supply it through your local environment as `LINKTRAIL_TOKEN`; MCP OAuth stays in the MCP client.

## Verify your account context

Replace the workspace placeholder with the workspace you selected when creating the credential:

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

Read the returned project identifiers. Use one of those identifiers in project-scoped operations. A workspace header selects context; it does not grant access to that workspace.

## Use shared commands

<Note>
  The generic command API needs a matching hosted release. Consult [capability status](/capability-status) before using these routes. Resource routes have their own release history.
</Note>

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

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

The POST body is the operation's argument object. [Operation reference pages](/mcp-tools/generated/overview) show the same logical request through HTTP, MCP and CLI. Follow the documented resource alias when you need its download format or status behavior; do not derive URL names from tool names.

## Handle errors before retrying

Read the HTTP status and structured error code. A 401 requires valid authentication; a 403 requires the right role, scope and project grant. For a queued write, reuse its idempotency value and unchanged arguments after a network failure. A successful queue response requires a later job read before you can claim a verification result.

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