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

The generic command API needs a matching hosted release. Consult capability status before using these routes. Resource routes have their own release history.
The POST body is the operation’s argument object. Operation reference pages 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, pagination and jobs, or error recovery.