canonical: https://jentic.com/apis/agentlinkops.com/agentlinkops

# AgentLinkOps HTTP API

The AgentLinkOps API manages a backlink program as a set of commands, covering placement classification, rank tracking, disavow rules, and competitor monitoring. It classifies link placements and reconciles retained suggestions, schedules rank checks and reports rank history, and monitors a domain's baseline backlink candidates. Disavow rules can be proposed, reviewed, imported, and exported, and competitor sets can be created and refreshed on a schedule. Each tracked link carries a lifecycle with renewals and a report, and observation evidence is retained per placement.

## For AI agents

Classify backlink placements, schedule rank checks, manage disavow rules, monitor competitors, and track link lifecycles across a backlink program.

## Scope

Does not run paid search ads, send outreach email, or host your website content. Use for backlink placement, rank tracking, disavow, and competitor monitoring only.

## Capabilities

- Classify a backlink placement and reconcile the retained suggestion
- Schedule rank checks and read rank history for tracked links
- Monitor a domain's baseline backlink candidates and read the monitor receipt
- Propose, review, import, and export disavow rules
- Create and inspect competitor sets and configure competitor refresh
- Track a link's lifecycle, record renewals, and read a lifecycle report
- Pull link reports and read observation evidence for a placement

## Use cases

### Agent-Run Backlink Operations

An AI agent connecting through Jentic can run a backlink program as discrete commands: classify a placement, schedule a rank check, or propose a disavow rule, each as its own call. Jentic injects the bearer token at call time and returns the matching command's input schema, so the agent runs the right operation without browsing a 271-command reference by hand.

Example prompt: Classify a new backlink placement, then create a rank schedule for the link so its position is tracked over time

### Rank Tracking and History

Track where links rank and keep a history of their movement. The AgentLinkOps API creates and updates rank schedules, lists existing schedules, and returns rank history so a reporting agent can show how a placement's position has changed. Schedules run on their own cadence and the history is queryable per link.

Example prompt: Create a rank schedule for a tracked link, then list its rank history to report the position trend

### Disavow and Competitor Monitoring

Keep a link profile clean and watch the competition. The AgentLinkOps API proposes, reviews, imports, and exports disavow rules so toxic links can be managed, and creates competitor sets with a configurable refresh so an agent can monitor rivals' backlink baselines and surface new candidates worth matching.

Example prompt: Propose a disavow rule for a flagged domain, then create a competitor set and configure its refresh to monitor rival links

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/commands/classify_placement` | Classify a backlink placement |
| POST | `/v1/commands/create_rank_schedule` | Create a rank schedule |
| POST | `/v1/commands/list_rank_history` | List rank history for a link |
| POST | `/v1/commands/propose_disavow_rule` | Propose a disavow rule |
| POST | `/v1/commands/create_competitor_set` | Create a competitor set |
| POST | `/v1/commands/monitor_domain_baseline_candidates` | Monitor selected baseline candidates |
| POST | `/v1/commands/get_link_reports` | Get link reports |

## Key resources

- **Placements** — Prepare, review, classify, and reconcile backlink placement context and classification jobs
- **Rankings** — Create, list, and update rank schedules and read rank history
- **Disavow** — Propose, review, import, export, and delete disavow rules and list disavow exports
- **Competitors** — Create and inspect competitor sets and configure or pause competitor refresh
- **Link lifecycle** — Track link lifecycle state, record renewals, and read lifecycle reports and link reports

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 46 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 45 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 37 / 100
  - Agent Usability: 43 / 100
  - Security: 60 / 100
  - AI Discoverability: 46 / 100
- **View full report:** https://jentic.com/apis/agentlinkops.com/agentlinkops/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the AgentLinkOps API by hand means handling its bearer API token, a separate human session token, and the 271 command routes yourself. Through Jentic you install once, import AgentLinkOps from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which AgentLinkOps commands your agent may call, and each command is its own URL path (such as `/v1/commands/list_rank_history`), so a rule can allow read commands while destructive ones like delete_resource or delete_disavow_rule stay out unless you add them.
- **Credential handling:** Your AgentLinkOps token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'classify a backlink placement' or 'track rank history', and Jentic returns the matching AgentLinkOps command with its input schema so the agent calls the right route without scanning 271 commands.

## Related APIs

- **Ahrefs** — Ahrefs provides backlink indexes, rank tracking, and site audits.
- **Semrush** — Semrush covers SEO, keyword research, and competitor analysis.
- **Moz** — Moz offers link metrics, domain authority, and rank tracking.

## FAQ

### What authentication does the AgentLinkOps API use?

The AgentLinkOps API authenticates with bearer tokens per its OpenAPI spec: an API token sent as a bearer token for programmatic calls, and a separate human session token. A free link check endpoint needs no token. Through Jentic the token is injected at call time rather than living in the agent's prompt or logs.

### Can I track link rankings over time with the AgentLinkOps API?

Yes. You create a rank schedule for a link, list and update existing schedules, and read rank history to see how a placement's position has moved. Schedules run on their own cadence, so a reporting agent can pull the history whenever it needs to build a report.

### What are the rate limits for the AgentLinkOps API?

The OpenAPI spec does not specify rate limits. Check the AgentLinkOps documentation at https://docs.agentlinkops.com for current limits before scheduling a large batch of rank or classification commands.

### How do I classify a backlink placement with the AgentLinkOps API through Jentic?

Search Jentic for 'classify a backlink placement' and it returns the classify_placement command with its input schema. Your agent sends the placement context and reads back the classification, then can reconcile the retained suggestion. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the AgentLinkOps API?

Yes. Each command is its own URL path, such as `/v1/commands/list_rank_history`, so a rule can allow read commands like listing rank history or link reports while write commands like delete_resource or delete_disavow_rule stay out unless you add them, and every action it takes is logged.

### Is there an AgentLinkOps MCP server?

You don't need an MCP server to give your agent the AgentLinkOps API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the classification, rank, disavow, and competitor commands on demand without loading 271 command definitions into its context.