Skip to main content
AI Visibility3 min read

Create a Cituna API key for scripts, CI and dashboards

Generate a personal API key to use Cituna from a script, a CI job, a Looker Studio dashboard or a local MCP install, and know when you do not need one at all.

An API key lets something other than your browser act as you: a nightly script that exports scores, a CI job that checks visibility before a release, the Looker Studio connector, or a local MCP install running in an environment where a browser sign-in is not possible. Keys begin cituna_sk_ and are shown exactly once, because they are stored hashed rather than encrypted: Cituna can check a key but cannot reproduce it. Before you generate one, check whether you need it: if you are connecting Claude or ChatGPT to Cituna interactively, the hosted MCP connector uses a browser sign-in and needs no key at all, which is one fewer secret to rotate.

1. Check whether you need a key

For Claude on the web, mobile, Desktop or Code, and for ChatGPT, add the hosted connector at https://mcp.cituna.com/mcp instead. It authorises through your browser and creates no long-lived secret.

Generate a key when there is no browser in the loop: scripts, scheduled jobs, CI, or the Looker Studio connector.

Cituna tracked prompts: each buyer question with one mark per AI engine, ticked where that engine named the brand, and how many engines named it
In Cituna: every tracked prompt, with a mark for each engine that named you. Example workspace.Try it on your site

2. Generate the key

Open Integrations → Claude / MCP access and click Generate token under API keys. The card shows the key once. For Claude Code, Cursor or Codex, pick the app on the same card and click Copy setup prompt instead: it makes a key named after the app and puts it in a prompt the app applies itself.

Copy it immediately. It cannot be shown again; if you lose it, revoke it and generate another. The card lists each key by its first and last characters, with the day it was made and when it was last used, so note which key went where.

3. Store it as a secret, never in the repo

Put it in an environment variable or your CI secret store. A key committed to a repository is a key that has to be rotated, even in a private repo.

Keys act with your workspace permissions, so treat one like a password rather than like a public identifier.

Environment variable

CITUNA_API_KEY=cituna_sk_your_key_here
Cituna sources: the sites AI engines cite for the tracked prompts, with citations per site, the change this period and the engines citing each one
In Cituna: the sites AI engines cite for your prompts, with each one’s citations and their change this period. Example workspace.Try it on your site

4. Use it

For a local MCP install, pass it as CITUNA_API_KEY in the server config. For the Looker Studio connector, paste it on the connector's key screen.

MCP calls are metered separately from the underlying scan and Search Console meters, so you can see automated volume distinctly from what you do in the app.

5. Rotate and revoke deliberately

Revoke a key the moment the thing it was made for is retired, and whenever someone with access to it leaves. Revocation is immediate.

Give each script or service its own key, so rotating one never takes down the others.

Troubleshooting

My key is rejected as invalid or expired.

Check three things before assuming the key is wrong. A stale local install of the MCP package can send an old auth header, so re-run with npx -y. A proxy or redirect between http and https will strip the Authorization header. And a key that was revoked stays revoked; generate a new one rather than re-pasting.

What can a key do that I cannot undo?

Write actions are limited to your own workspace: starting a scan, which uses your monthly quota; adding, turning off or deleting tracked prompts; queueing, editing or marking articles published; taking topics out of the queue; and moving gaps and outreach targets. Write access needs Pro or Max; on Starter a key is read-only. Two can reach your website, both through the destination connection you already made: refreshing a live AutoSEO article rewrites its title, description and FAQs there, and a queued article is delivered like any other, so with Publish automatically it goes live.

Can I scope a key to one brand?

Not today. Keys carry your workspace permissions. If you need narrower access for an agency client, a separate workspace is the supported boundary.

I lost the key. Can support retrieve it?

No, and that is deliberate. Keys are stored hashed, so nobody, including us, can read one back. Revoke the lost key and generate a replacement.

Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.

Rahul Arora

Written by

Founder, Cituna

Rahul founded Cituna and leads the product. He runs Cituna on his own sites first, in the same workspace customers use.

Find your next AI visibility fix with Cituna

Cituna asks ChatGPT, Perplexity, Gemini, Claude, Grok, Google AI Overviews and Google AI Mode your buyers' questions every day, writes the fix for every answer you are missing from, and publishes new articles to your site. Run all of it from Claude or any AI agent.

  • Your buyer questions asked on 7 AI engines every day
  • Which answers name you, and which name a competitor
  • The pages each engine cites instead of you
  • A written fix for every answer you are missing from

3-day free trial · Card required, cancel anytime · Plans from $49 a month

Join 1,783 growing businesses

The Cituna overview: visibility score, its trend and the result on each AI engine