Connect Ahrefs to Codex
Give Codex governed access to Ahrefs’s 135 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ahrefs to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Ahrefs in Runlayer
Add Ahrefs from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Ahrefs’s 135 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Ahrefs
Sign in the way Ahrefs requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Ahrefs from Codex
Ahrefs’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
135 Ahrefs tools in Codex
Runlayer policy decides which of these Codex users can call. 93 read data only.
Batch analysis
Performs a batch analysis of multiple URLs, domains, or subdomains to retrieve selected SEO, backlink, organic, and paid traffic metrics.
Brand radar AI responses
Provides questions asked to AI assistants and the corresponding AI-generated responses that mention your brand or competitors’ brands, including cited sources and search volume estimates.
Brand radar AI responses entities
Provides questions asked to AI assistants and the corresponding AI-generated responses that mention your brand or competitors’ brands, including cited sources and search volume estimates.
Brand radar citations history entities
Provides the historical number of citations for your and competitors' brand URLs in an LLM you specify.
Brand radar citations overview entities
Provides the number of citations for your and competitors's brands in an LLM you specify, with filters for locations, query text, URL, and more.
Brand radar cited domains
Provides domains cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each domain (broken down by brand) and…
Brand radar cited domains entities
Provides domains cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each domain (broken down by brand) and…
Brand radar cited pages
Provides the pages cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each page (broken down by brand) and…
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Ahrefs call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more