Backlink Research
Pull backlink evidence for an agent-defined SEO investigation; StackOS captures Ahrefs API-unit headers while monetary budget enforcement remains disabled until API units are modeled.
Organic keyword and backlink research provider; requires eligible API access and API units.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
2 matching actions
Pull backlink evidence for an agent-defined SEO investigation; StackOS captures Ahrefs API-unit headers while monetary budget enforcement remains disabled until API units are modeled.
Pull competitor organic keyword evidence for agent analysis; StackOS captures Ahrefs API-unit headers while monetary budget enforcement remains disabled until API units are modeled.
Direct answer
People continue using Ahrefs as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 2 Ahrefs actions across SEO Research. The exact actions used depend on the workflow and approval rules.
No. Ahrefs remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.