Skip to main content
Hosted work needs pilot eligibility, an authorized workspace and the required project access and scopes. Installing the CLI or a skill does not grant access. For one local supplied-link check, you need network access but no AgentLinkOps account, repository, ledger, CRM or publisher recipe. It returns a dated observation with evidence limits.

​
Service health and support

Open the health endpoint for a live response from the service. A reply with "status":"ok" means the service answered. It doesn’t test every feature or your workspace access. If you can’t sign in, open AgentLinkOps directly and check that you are using the account your workspace invited. Your role, website access and plan decide which actions you can take. Security and data explains roles and scopes. For anything else, email support@agentlinkops.com with what you were trying to do, when it happened and any request reference the app showed. Leave passwords and API keys out of the message.

​
Data and delivery requirements

Reports describe the selected tracked or imported dataset. Missing corpus or supplier rows cannot establish whole-web absence. A configured schedule does not guarantee an exact completion time. The owned discovery corpus is stopped. Supplier-backed backlink lookups are a separate capability; they do not depend on that corpus. A documented research or analysis command can remain unavailable even when supplier lookups are available. Read the current offer and connected catalog for your workspace.

​
CLI and skill choices

The CLI is available from npm under the Apache-2.0 license and requires Node.js 22.13 or later. Inspect npx -y agentlinkops --help for the installed version’s commands.Current agent setup defaults to the connection skill and its reference. Add optional skills or recipes with --skill ID or --recipe ID; choose --all-skills explicitly for the complete pack. Older releases can install the full pack. Your editorial method, tools and record system remain yours. Quickstart explains the separate installation routes and selections.Skill installation writes supported client settings or prints manual instructions; it stores no credential. Current source can offer a separate CLI key connection after setup. See CLI setup version support before using that flow. agent status describes configuration. A successful product read verifies that read; package and configuration checks alone do not establish hosted access.

​
Choose the hosted connection

CLI OAuth uses MCP for product calls. Its credential store requires Linux; macOS and Windows CLI OAuth are refused. A successful OAuth connection verifies workspace/project reads and leaves write permission unverified. Use an API key in the terminal or your MCP client’s OAuth flow on other platforms.

​
Read the connected catalog

List your projects through MCP or inspect the HTTP catalog. The catalog describes registered operations. Workspace membership, project grants, scopes and provider admission still govern each call. Operator-only toolsets (admission, library, rank and licensed) and the discover_backlinks command are hidden from ordinary authenticated catalogs. Their presence in documentation or a bundled snapshot does not grant access, and adding scopes does not reveal them. The default MCP view lists exec and discovers commands on demand. CLI and HTTP use the same canonical command names. Use those names for new connections; compatibility names retain their recorded windows. The command reference and release manifest separate source contracts, dated deployment evidence and historical authenticated readback. Documentation coverage does not prove that every command was executed in your environment. Consult the connected catalog when those records differ.

​
Keep records and interpret evidence

Use the optional ledger for records, reports and declared action receipts. The separate local stdio MCP host has eight repository-context tools; they are absent from hosted MCP and HTTP. AgentLinkOps keeps prospects, private contacts and externally recorded outreach outcomes. Your agent researches fit and prepares drafts. Your sender keeps messages and delivery records; AgentLinkOps sends no outreach email. An existing external CRM is optional. Campaign workflows and the CRM handoff describe that division. An accepted job is queued work. Read its terminal result before reporting an observation. A blocked fetch stays unknown, and one absent observation does not establish confirmed loss. A published email address has no deliverability guarantee. A competitor placement does not establish that a publisher will accept your proposal. Read evidence states, usage and jobs and error recovery when a required operation cannot complete.