cogny cliseofirst 15 calls free

ahrefs from the shell.

Pull Domain Rating, backlinks, referring domains, organic keywords, top pages and SERP overviews from the Ahrefs API v3 — straight from Bash. No CSV exports, no manual Site Explorer clicking, just the Cogny CLI over the Ahrefs MCP.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Ahrefs toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Ahrefs__domain_rating --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Today you open Ahrefs Site Explorer, run a report per tab, and export CSVs you then stitch together by hand. The CLI returns the exact rows you ask for as JSON you can sort, diff, or pipe into an agent in one call. Connect Ahrefs once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Ahrefs tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Ahrefs tools.

Tool names as the Ahrefs MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Ahrefs__domain_rating
Domain Rating (0-100) for any target domain.
- cogny tools call mcp__Ahrefs__domain_rating \ --input '{"target":"example.com"}'
example response
```
{
  "domain_rating": {
    "domain_rating": 74,
    "ahrefs_rank": 18422
  }
}
```

mcp__Ahrefs__organic_keywords

Keywords a target ranks for, with volume, position and traffic.

cogny tools call mcp__Ahrefs__organic_keywords \ --input '{"target":"example.com","country":"us","limit":3,"order_by":"traffic:desc"}'

example response

{
  "keywords": [
    {
      "keyword": "running shoes",
      "volume": 49500,
      "position": 4,
      "url": "https://example.com/shoes",
      "traffic": 3120
    },
    {
      "keyword": "trail running shoes",
      "volume": 22200,
      "position": 2,
      "url": "https://example.com/trail",
      "traffic": 2840
    },
    {
      "keyword": "best running shoes 2026",
      "volume": 14800,
      "position": 6,
      "url": "https://example.com/best",
      "traffic": 910
    }
  ]
}

mcp__Ahrefs__backlinks

List backlinks pointing to a target, newest first.

cogny tools call mcp__Ahrefs__backlinks \ --input '{"target":"example.com","mode":"domain","limit":2,"order_by":"domain_rating_source:desc"}'

example response

{
  "backlinks": [
    {
      "url_from": "https://nytimes.com/wirecutter/shoes",
      "url_to": "https://example.com/",
      "anchor": "best running shoes",
      "domain_rating_source": 93,
      "first_seen": "2026-04-02"
    },
    {
      "url_from": "https://runnersworld.com/gear",
      "url_to": "https://example.com/trail",
      "anchor": "trail picks",
      "domain_rating_source": 81,
      "first_seen": "2026-03-18"
    }
  ]
}

03tools list

the rest of the surface.

A sample of the other Ahrefs tools. Run cogny tools list --json for every tool and its input schema.

mcp__Ahrefs__subscription_info
mcp__Ahrefs__backlinks_stats
mcp__Ahrefs__refdomains
mcp__Ahrefs__site_explorer_overview
mcp__Ahrefs__organic_competitors
mcp__Ahrefs__top_pages
mcp__Ahrefs__keywords_explorer
mcp__Ahrefs__serp_overview
mcp__Ahrefs__batch_analysis

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Ahrefs CLI?: No — it is the Cogny CLI calling the Ahrefs MCP over the cogny-mcp-proxy. You connect your Ahrefs API token once inside Cogny and then call every endpoint from Bash. No bespoke API client to wire up.
Does it use my Ahrefs API units?: Yes. The proxy calls the Ahrefs API v3 with your token, so each call consumes your account/subscription units exactly as a direct API call would. Use `subscription_info` to check remaining units.
Can my coding agent run these calls?: Yes. After `npx @cogny/cli init` issues a key, an agent can call `cogny tools call mcp__Ahrefs__organic_keywords --input ...` from any shell — no MCP wiring or restart needed.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

ahrefs, then a verdict.

Start free All CLIs