Ask your assistant whether the answer engines can see a website, and get a
number back.
> Can ChatGPT actually find stripe.com, or is it invisible?
analyze_site(url: "stripe.com") → run_id: cm4x…
get_analysis(run_id: "cm4x…") → Score: 78/100
The audit reads a live site the way an assistant does — the identity files an
engine looks for (, and the rest), the crawler policy, the
schema graph, page health — and then asks Claude, ChatGPT, Gemini and
Perplexity whether they name it. One score out of 100 across eight weighted
sections.
How ChatGPT, Claude, Gemini and Perplexity read a site: free check, fix plan, compare, history.
Three of the tools run entirely on your machine — a robots.txt fetched, a
file probed for, a page parsed. No account, no allowance, no call home.
> Is anything blocking AI crawlers on stripe.com?
check_ai_access(url: "stripe.com")
Retrieval: all 7 answer-engine crawlers may fetch the site.
Training: 3 of 8 blocked — Meta-ExternalAgent, Bytespider, Amazonbot.
The rest is inite.ai's AI visibility server, and it answers signed out too, as
a guest: check_identity, the fix plan (visibility_fixes), a competitor read
the same way (compare_sites), how the reading moved (visibility_history),
and analyze_site as the survey - the audit without its two paid steps, two a
day per address.
> What should firecrawl.dev fix first so ChatGPT can use it?
visibility_fixes(url: "firecrawl.dev")
1. [critical] No structured data on the site (about +3.5 points)
Do: Add Organization (and WebSite) JSON-LD to every page.
2. [high] 7 retrieval crawlers are blocked on …
Visibility and nothing else. INITE's services and booking are
ai.inite/inite,
the catalogue of AI tools is ai.inite/atlas.
Signing in makes the calls your account's: its tier of the audit (the teaser on
a free plan, the whole audit on a paid one) and your audits: my_reports, and
the fix plan and history built from them.
Install
Claude Desktop, Cursor, or any client that launches a stdio server:
That opens a browser, you approve, and the token is stored at
~/.config/inite/mcp.json with owner-only permissions. Authorization code with
PKCE over a loopback redirect, the flow RFC 8252 prescribes for a native app.
Nothing is written to the repository and no secret ships in the package.
Already have a token (CI, a shared config, a container):
Client speaks remote MCP? Skip this package. Point it straight at
https://inite.ai/api/mcp/analyzer: every open tool answers without a token,
and a member tool answers 401 with WWW-Authenticate naming
the protected-resource metadata,
which names the authorization server.
Tools
Local — no account:
tool
what it does
check_ai_access(url)
Which AI crawlers robots.txt lets in, separating the ones that fetch a page to answer a live question from the ones that only collect training data. Blocking the first kind is what makes a site invisible; blocking the second costs nothing.
check_identity_files(url)
Which of the ten identity files exist — llms.txt, ai.json, identity.json and the rest.
check_page_signals(url)
Title, description, canonical, hreflang, and the Schema.org types in the page's JSON-LD.
Remote — open without an account, more with one:
tool
what it does
check_identity(url)
Free and instant: which answer-engine crawlers get in, the identity files, structured data, an identity score out of 100 and what that reading says to fix. No model asked.
visibility_fixes(url)
The fix plan, most important first: what to change, why, how many points it should recover, the pages it applies to, and a paste-ready file when there is one. Signed in, built from your latest audit of the site.
compare_sites(url, other)
Your site and a competitor's, read the same way, side by side, and who is ahead on each count.
visibility_history(url)
How the reading moved: the INITE Atlas's weekly readings for a site it carries, and your own audits.
analyze_site(url)
Starts the audit that also asks the answer engines whether they name the site, and returns a run_id. A survey without an account, the teaser on a free plan, the whole audit on a paid one.
get_analysis(run_id)
Progress while it runs; the score out of 100 and what to fix first once it finishes.
my_reports()
Signed in: your audits, newest first.
Two tools rather than one for the audit, because it is asynchronous. A single
tool that blocked for a minute would be torn down by most clients' timeouts.
Commands
inite-visibility run as an MCP server over stdio (what a client does)
inite-visibility login sign in through the browser
inite-visibility whoami say whether a usable token is present
What this package is
Two halves.
The local checks are real work done here: fetching, parsing, and the robots
rules applied properly — most-specific group wins, longest matching rule wins,
Allow breaks a tie. They cost nobody anything because your machine does them.
The remote half defines no schemas of its own. It asks inite.ai what it
offers and forwards calls there, so that tool list is whatever the service
implements today. A local copy would be a second source of truth, and the first
thing it would do is drift.
What stays on the server is what costs something or is ours: four answer
engines asked whether they name a site, and the weights that turn everything
into one number. The local tools report facts; analyze_site reports a score.
Account and allowance
Without an account every open tool answers, under a per-address allowance: the
identity check, the fix plan, the comparison and the history, and the audit as
a survey, two a day. An account makes the audit its plan's own, exactly as on
the website: the teaser on a free plan, the full pipeline - four answer engines
asked - on a paid one. Plans are here.
Environment
variable
meaning
INITE_TOKEN
Use this token instead of the stored one.
INITE_MCP_URL
Point at a different endpoint. Default https://inite.ai/api/mcp/analyzer.
INITE_TOKEN_FILE
Where the token lives. Default ~/.config/inite/mcp.json.
Published to the MCP registry as ai.inite/inite-visibility, a namespace held
by proving control of inite.ai — the public half of the key is served at
/.well-known/mcp-registry-auth.
Named by the domain rather than the code host on purpose: a service whose whole
job is being legible to machines should tell them who it belongs to in its own
name.
A note on the command name
npx @inite/visibility resolves because there is exactly one binary in the
package. npm looks for a command matching the package name with the scope
stripped — visibility — does not find it, and runs the only one there is.
The binary is called inite-visibility rather than visibility on purpose: a
scoped package has no business claiming a word that general in your PATH on
a global install. The cost is that a second binary would break the line above
for every client, so a test pins it at one.
If you are invoking it from a directory that contains this package's own
package.json, npm prefers the local copy and finds no linked command. Name it
explicitly there:
npx -p @inite/visibility inite-visibility login
Development
npm install
npm run build
npm test
The tests cover what the bridge can get wrong without saying so: dropping the
credential, turning "signed out" into "broken", swallowing an error into a
success, and letting a stale file beat the environment.
Contribute with an AI agent
You don't need to be an engineer. Open the repo in your coding agent and say
/contribute (Claude Code) — or "read AGENTS.md and help me add …" in any
other agent. AGENTS.md holds the rules, the commands CI runs and
the idea → PR loop; CONTRIBUTING.md is the short version.
Only want to suggest something? /spec-idea, or the
Product idea
form.
INITE's services as a ladder, cheapest first: each step's name, what it delivers, how long it takes, its price in the reader's currency and whether that price is fixed, a floor or monthly, whether the fee is refunded if the work concludes nothing should be built, and how it starts - a call to book w
The call times INITE's calendar has free, as ISO instants, with the call length and the host's time zone. Pass one of them to inite_book_call as starts_at.
Book a call with the INITE team for a named person. starts_at must be a slot from inite_slots; topic is a service id from inite_services (default: diagnostic). The person receives a confirmation email with a calendar invite and a link to move or cancel. Book only with the person's consent and their
Send a message to the INITE team on behalf of a named person; the reply goes to their email. For a question that needs a conversation, inite_book_call is faster.
INITE's guides (PDF, a few pages each): their titles, what each covers and its page. Pass slug and email to send one to a person - they receive the PDF by email, and only with their consent.
The signed-in account's plan, its daily audit allowance and how much of it the last 24 hours used, and how many Atlas tools it owns. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Start a purchase of a one-time INITE offer for the signed-in person. Returns a checkout link for the person to pay (nothing is charged until they do) and, when card-free payment is on, an x402Url: an agent connected to the person's INITE wallet (https://billing.inite.ai/mcp/wallet, scope wallet:pay)
Free and instant, no account: read a website the way an AI engine does before it ever answers about it. Returns which answer-engine crawlers robots.txt lets in (retrieval, which decides whether the site can be cited) and which training crawlers it blocks (which costs nothing), the identity files pre
The AI visibility audit: the identity files, crawler policy, schema graph and page health, then the answer engines asked whether they name the site, scored out of 100. Starts a run and returns its run_id; it takes about a minute, so call get_analysis with that id. Without an account it runs the surv
Read an audit started by analyze_site: progress while it runs, then the score out of 100 and what to fix first. Only the caller who started the run can read it - the account, or for a guest the same address.
The signed-in account's AI visibility audits, newest first: the site, the day, the tier, the score and the report's address. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Find AI tools that fit a described job, from the INITE Atlas - ten thousand tools re-read every week, ranked by measured use rather than votes. Describe the job in a sentence or two with any constraint that matters (self-hosted, an API, a free plan, a budget, who will use it). Returns up to five too
One AI tool from the INITE Atlas, by domain or name: what it does and who it is for, the starting price with the pricing page and the day it was read and how the price has moved, how a program reaches it (API docs, an OpenAPI document that parses and its path count, an MCP server in the official reg
Filter the INITE Atlas without a model: a phrase, a category, and slices that must all hold. Categories: sales, hr, security, analytics, agents, support, dev, llmops, finance, automation, marketing, meetings, knowledge, rag, voice, documents, legal, data, health, i18n, creative, writing, productivit
What changed among the tools in the INITE Atlas: prices up or down, free plans added or dropped, OpenAPI specs published, MCP servers listed. Each change was read twice from the vendor's own page or the public registry before it counts, and a correction somebody typed in is never reported as the ven
Live discount codes for AI tools in the INITE Atlas, optionally for one domain. Each was stated by somebody who proved they own the domain, and carries the day they last confirmed it - quote that day. INITE does not run other companies' checkouts: never call a code verified or tested.
The tools the signed-in account has claimed in the INITE Atlas: whether each claim is verified and how, whether the badge link is still on the site, premium until when, and the card address. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Start (or resume) a claim on a tool's Atlas card for the signed-in account. Answers with three ways to prove the domain - a badge link on any page of the site, a meta tag on the homepage, or a DNS TXT record - each with the exact snippet. If the account's email is on the domain and verified, the cla
Check the proof placed for a claim: method "badge" (with pageUrl, the page the badge link is on), "meta" (the homepage meta tag) or "dns" (the TXT record). Answers verified, or what was missing. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
For a tool the account has claimed: what the card prints and what it could not read - price, hiring, releases, company - with the page each was read from and what to do about each empty line. Plus the claim's status and premium. Needs a signed-in inite.ai account: a guest call answers 401 and starts
For a proved owner: name the pricing page, the careers page and the changelog or release notes, on your own domain. The Atlas reads them with its usual readers and guards - a price must be printed on the page, a job board must be your own, release notes must carry dates - and never takes a figure on
Re-read the claimed site now - activity, hiring, releases, crawler policy, identity files - with the pages you named. Once a week on the free tier, once an hour on premium. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Views of the card and clicks through to the site: thirty days on the free tier; ninety days and the shelf beside it on premium. With what Google showed of the card last month (impressions, clicks, top queries) and its neighbours on the shelf. Needs a signed-in inite.ai account: a guest call answers
Propose a correction a person at INITE reviews before it shows: field "name" (with name), "pricing" (with pricing: {model, freeTier, startsAt: {amount, currency, per} | null, source: the page it is on}) or "note" (with note, free text to the editors). Our one-line description and verdicts are not ed
The coupons this claim has published, live or not, with their ids for atlas_owner_coupon_set. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
For a proved owner: publish a discount on the card and the Atlas coupon feed, shown as stated by the verified owner. Needs title (one sentence), endsAt (ISO date, within a year), url (a page on your domain where it applies), and kind with code, percentOff, amountOff+currency or trialDays as fits. Co
action "confirm" says the coupon still works (it stops showing 45 days after the last confirmation); "withdraw" takes it down. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
What premium adds (re-reads hourly, ninety-day stats with the shelf beside the card) and the link where the owner pays - checkout is a card form in a browser, not an agent action. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Give up the claim on a card. The card stays in the Atlas; the owner mark, coupons and owner tools go with the claim. A later claim needs a fresh proof. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Preview a price comparison of 2-5 Atlas tools for a usage scenario, computed without a model from plan editions checked against the vendors' own pricing pages. First category: AI transcription (seats, minutes a month, required capabilities). Returns per tool the cheapest fitting verified plan, or wh
Save a comparison as a private draft dataset in the signed-in account: tools, required capabilities, the default scenario. Returns the dataset id, configVersion and a preview with coverage. Nothing is public until atlas_dataset_publish. Needs a signed-in inite.ai account: a guest call answers 401 an
Change a dataset the account owns: title, language, tools, required capabilities or default scenario. Names the configVersion it read; a newer one is VERSION_CONFLICT. A published set keeps serving its published config until atlas_dataset_publish. Needs a signed-in inite.ai account: a guest call ans
Make the named configVersion of a dataset public: cuts an immutable revision and returns the public API, page and compare URLs plus install notes. Call it only when the user asked for a public comparison. Needs at least two tools with verified plans. Needs a signed-in inite.ai account: a guest call
Read a dataset: a published one by anybody (its snapshot with freshness and the default result), a draft only by its owner (config, configVersion, preview). Optional revision reads history.
Confirmed changes between the revisions of a published dataset, newest first: plans added, removed, or which fields moved. Page with `after` (a revision number).
Stop serving a dataset the account owns. The API then answers 410 with a fallback line, so a page that still reads it degrades instead of breaking. Already-downloaded snapshots cannot be recalled. Needs a signed-in inite.ai account: a guest call answers 401 and starts the OAuth flow.
Tell the Atlas which public page shows a published dataset, and check it now: the page's HTML must carry the data and a visible link to the dataset page (not in a comment, iframe or noscript). Re-checked daily; the state shows in atlas_dataset_get. Nothing on the page is changed. Needs a signed-in i
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt INITE Visibility einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: INITE_TOKEN.
Welchen Transport verwendet INITE Visibility?
INITE Visibility wird über HTTP erreicht.
Wann wurde INITE Visibility zuletzt geprüft?
Zuletzt geprüft: 2026-10-18. How ChatGPT, Claude, Gemini and Perplexity read a site: free check, fix plan, compare, history.