> ## 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. # What you can use today > Check AgentLinkOps pilot access, shared MCP, CLI and HTTP commands, optional local workflows, and the data and delivery settings required for your task. AgentLinkOps provides hosted backlink monitoring, imported candidate checks and dated evidence through MCP, CLI and HTTP. Hosted access is limited to the private pilot. Public signup and payment collection are not active. Last reviewed: September 15, 2026, against production version `edbb3301`. ## Hosted private pilot With pilot access, [connect your agent](/guides/connect-mcp) or [use HTTP](/guides/connect-http), then list your accessible projects. Your workspace membership, project grants and scopes control what you can read or change. Installing a skill does not grant account access. The pilot supports supplied-URL monitoring, destination checks, history, saved-page contact evidence, reports, backlink imports and selected candidate verification. Start with [one supplied placement](/guides/check-placement) or [an import you already hold](/guides/import-and-verify). ## Shared command and batch release boundary Production version `ba77c919-aa2d-47a2-9493-c77a085e3a7e`, deployed September 16, 2026 at 17:08 UTC from source commit `0a9a796`, serves 86 authenticated commands shared across MCP, generic HTTP and CLI `tools` / `describe` / `call`; nine retired command names (`get_link_history`, `get_target_history`, `get_link_evidence`, `get_target_evidence`, `get_target_job`, `request_link_check`, `request_target_check`, `list_link_events`, `list_target_events`) resolve to their canonical commands as aliases for twelve months. The MCP server serves explicit views (`/mcp` bounded default, `/mcp/all`, `/mcp/{toolset}`, `/readonly`, `/mcp/code`); MCP list rows are concise by default (`format: "detailed"` restores every field); the skill discovery index and the [agent reference](/reference/agent-reference) are served on `app.agentlinkops.com` and `agentlinkops.com`. Verified by a byte-identical download of the deployed script and authenticated calls; the receipt is `docs/acceptance/2026-09-16/main-release-ba77c919/` in the product repository. The follow-up `1ed1783d` (assets only) made the skill discovery index self-contained on every host, and `agentlinkops` 0.5.0 is on npm. Earlier: Production version `edbb3301-0fe0-4b69-9a2f-d2eb65c1fb1e`, deployed September 15, 2026 at 13:50 UTC from source commit `fb95463`, serves 73 authenticated commands shared across MCP, generic HTTP and CLI `tools` / `call`. Those are the 71 commands in the verified September 14 parity bundle plus `preview_resource_deletion` and `delete_resource`. The count comes from the deployed source, its parity gate and the release receipt, not from a fresh authenticated catalog read. The earlier authenticated catalog check is historical; reconnect to inspect the current endpoint. Refresh your client's `tools/list`, or read `GET /v1/commands` with your credential, before using a command. The [command index](/reference/index) provides its inputs and required scopes. A registered command can still depend on a configured provider or delivery setting. Three documented commands remain development previews: batch verification (`verify_discovery_candidates`, `get_candidate_verification_batch`) and candidate enrollment (`monitor_discovery_candidate`). Use [single-candidate verification](/reference/commands/verify_discovery_candidate) for current imported-candidate work. Unused-resource cleanup (`preview_resource_deletion`, `delete_resource`) is deployed; it removes never-executed scratch resources only and does not erase history. The preceding version `977394dd` (September 15, 2026, 13:33 UTC) carried the audit corrections that earlier reference pages described ahead of release. Configuration errors such as `PROVIDER_NOT_CONFIGURED` return `retryable: false`, `rotate_webhook_secret` explains the rotate-then-retire sequence when nothing is left to retire, member errors name the fix, `get_domain_mix_report` no longer returns vendor padding guidance, anchor reports use tokenizer version 2 with `tokenization.address_spans_removed`, and the import commands document their row schemas with row-level `accepted` and `created` counts. A connected client keeps its cached `tools/list` until it reconnects, so refresh the catalog before relying on the changed schemas. Version `edbb3301` renames the runtime identifiers to AgentLinkOps: the MCP servers register as `agentlinkops` and `agentlinkops-free`, and every webhook delivery carries the `AgentLinkOps-*` headers alongside the `Linktrail-*` set with identical values. The CLI executable is `agentlinkops` with `AGENTLINKOPS_*` variables and an `.agentlinkops/` ledger directory; the old names keep working as compatibility aliases until the dated cutover recorded under DP-0029-T05. ## Data and delivery still depend on configuration Read the server's `GET /config` [capability flags](/reference/http/protocol#configuration-and-operational-endpoints) before choosing a data or delivery workflow. These flags describe server configuration; they do not grant permission or prove data coverage. * **Discovery:** supplier access remains gated. Owned-corpus discovery, competitor inventory capture and recurring refresh have private-staging acceptance. Confirm the connected environment and coverage; imports remain an available source of candidates. * **Owned corpus:** coverage is limited to collected niches and pages. Missing inventory rows cannot establish whole-web absence. * **Webhooks and digests:** signed delivery has private-staging acceptance; production delivery remains disabled. Use [authenticated event feeds](/guides/monitor-changes) for changes. Saving an endpoint does not prove delivery. * **Google context:** manual inputs and imported snapshots work locally. A direct Google connection requires separate authorization and acceptance. Missing rows never mean zero impressions. ## Locally validated capabilities Local workflows are optional. They need an authorized checkout or supplied package; public download, licensing and marketplace publication remain pending. * **Checks and records:** the [CLI](/guides/connect-cli) can check a supplied URL pair without an account, then optionally keep a ledger, import rows, produce reports or sync with an authorized hosted project. Local checks need network access. * **Campaign preparation:** the [toolkit](/campaign-workflows) supports public-page research, qualified briefs, reviewed drafts and declared action receipts. Your agent supplies judgment and communication. The [CRM and sender guide](/guides/crm-sender-handoff) covers a portable handoff; it does not establish a tested vendor connection. * **Site context:** eight tools on a separate [local MCP host](/guides/local-context) read manual inputs, imported Search Console context and site facts. They do not run on the hosted product endpoint. ## Who does what AgentLinkOps records observations. Your agent researches fit and prepares drafts; your CRM and sender keep their own relationship, delivery and reply records. Local notes remain under your control. A blocked fetch stays unknown. A published email address has no deliverability guarantee. A competitor placement does not establish that a publisher will accept your proposal. Read [evidence states](/evidence) when interpreting results and [troubleshooting](/guides/troubleshooting) when a required operation is unavailable.