Skip to main content
Use https://app.agentlinkops.com with a workspace API key from the app’s Agent access area. An owner or admin creates the key in an eligible workspace. Supply it through your local environment as AGENTLINKOPS_TOKEN. OAuth credentials used by an MCP client or the Linux CLI OAuth flow do not authenticate these REST calls. The CLI still reads LINKTRAIL_TOKEN as a compatibility alias; HTTP requests use the bearer header below.

​
Verify your account context

Replace the workspace placeholder with the workspace selected for your credential:
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 explains credential creation and permission limits.

​
Use shared commands

Read the connected catalog to inspect command availability and inputs:
The index returns compact command rows. Add ?include=schemas for full definitions, or describe one command without a request body:
Then call the operation with its argument object as the POST body:
Command pages show the same operation through HTTP, MCP and CLI. Check availability 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. Generic command calls accept no query parameters or Idempotency-Key header. Supply idempotencyKey in the JSON body only when the command documents that field. After a lost response to such a write, reuse its accepted key 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. Keep the response requestId or X-Request-ID for diagnostics and honor Retry-After before retrying a rate limit. A curl example does not retry on its own. Continue with checking a placement, pagination and jobs, or error recovery.