AgentLinkOps HTTP API
46
AI ReadinessFoundational (D)46/100
Official vendor OpenAPI document · agent-readyMarketingSeo Sembearer271 EndpointsREST
For Agents
Classify backlink placements, schedule rank checks, manage disavow rules, monitor competitors, and track link lifecycles across a backlink program.
Use for: Classify a backlink placement, Schedule rank checks for a set of links, Monitor a domain's backlink baseline, Propose a disavow rule for a toxic link
Not supported: 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.
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.
Install Jentic One Beta
Connect the AgentLinkOps HTTP API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AgentLinkOps HTTP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fagentlinkops.com%2Fagentlinkops" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fagentlinkops.com%2Fagentlinkops" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AgentLinkOps HTTP API.
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
Patterns agents use AgentLinkOps HTTP API for, with concrete tasks.
★ 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.
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.
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.
Propose a disavow rule for a flagged domain, then create a competitor set and configure its refresh to monitor rival links
Key Endpoints
271 endpoints — the agentlinkops api manages a backlink program as a set of commands, covering placement classification, rank tracking, disavow rules, and competitor monitoring.
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
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
Jentic AI Readiness Score
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.
A
AgentLinkOps HTTP API
- Foundational (D)46/100
45
Foundational Compliance62
Developer Experience & Jentic Compatibility37
AI-Readiness & Agent Experience43
Agent Usability60
Security46
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
45
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
82%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
37
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
76%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
46
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: DSignals: 1
46%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AgentLinkOps HTTP API through Jentic.
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.
GET STARTED