Skip to main content
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:
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

Production version 977394dd (September 15, 2026) serves the generic command API. Read the connected catalog to inspect available commands and inputs:
Then call an 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. 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, pagination and jobs, or error recovery.