> ## 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

> See which AgentLinkOps campaign, research, monitoring and local toolkit capabilities are available in the private pilot and which still need release acceptance.

AgentLinkOps combines a hosted private pilot with local campaign and repository tools. This page separates those surfaces so a feature in source code does not become a promise about your connected account.

Last reviewed: September 13, 2026.

## Hosted private pilot

The pilot provides scoped workspace access, supplied-URL monitoring, destination checks, dated history, saved-page contact evidence, reports, backlink imports and selected candidate verification.

Connect at `https://app.agentlinkops.com/mcp` using the [quickstart](/quickstart). Public signup and payment collection are not active. Your account, project grants and scopes determine which records and operations you can access.

The [generated tool reference](/mcp-tools/generated/overview) describes the source registry. Your client's `tools/list` response describes the tools registered on the connected endpoint. Neither count establishes that a data provider or notification transport is active.

## Locally validated capabilities

| Surface            | What it supports                                                                                | Availability boundary                                                         |
| ------------------ | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Ledger CLI         | Wanted and expected links, local checks, imports, status, diffs, reports and authenticated sync | Development checkout or supplied package; local checks need network access    |
| Campaign research  | Bounded public contact walks, unlinked mentions, outbound citation evidence and qualification   | Local modules validated on real pages; not all are hosted MCP tools           |
| Campaign briefs    | Markdown and structured action records, inspect/reject/defer decisions and local draft handoff  | Local toolkit; the customer's agent owns judgment and communication           |
| Content toolkit    | Sourced research and drafts, editorial review, text cleanup and link checks                     | Supplied local package; the customer supplies the agent and runtime           |
| Repository context | Manual site inputs, site facts and imported Search Console context                              | Eight tools on a separate local stdio MCP host; absent from hosted HTTP MCP   |
| Action receipts    | Customer-declared work, local receipt history and later observations                            | Local validation; an observation does not prove attribution or ranking impact |

Use [campaign workflows](/campaign-workflows) for the research jobs and [the ledger guide](/ledger) for local records. Public toolkit download, licensing and marketplace publication have separate release requirements. A validated package is not a public marketplace listing.

## Data and delivery still depend on configuration

* **Live discovery and competitor workflows:** provider-backed admission and release acceptance remain in validation. Customer imports do not imply whole-web coverage or a licensed supplier connection.
* **Owned discovery corpus:** coverage is bounded to the collected niche and pages. It is not a complete backlink index.
* **Webhooks and digests:** transports exist and have local validation. Hosted delivery requires the relevant environment configuration; creating an endpoint is not proof a notification was delivered.
* **Google context:** manual inputs and imported connector snapshots work locally. A direct Google connection requires its own authorization and acceptance. Missing rows never mean zero impressions.

## Who does what

AgentLinkOps records observations and preserves their limits. Your agent researches fit, uses your browser and search tools, prepares drafts and performs separately authorized communication. Your local records remain yours.

A blocked fetch stays unknown. A published address carries no deliverability promise. A competitor placement carries no promise that the publisher will accept your proposal. Read [evidence semantics](/evidence) before using a result to make a campaign decision.

Return to the [AgentLinkOps overview](/introduction) for the complete campaign flow.