Skip to content
Check my business

AEOHIT inside the tools you already use

Ask your AI assistant how visible a business is, start a scan, write the fixes and publish them, without opening the app. The same workspace, plan and rules as AEOHIT itself, across seven AI engines.

claude mcp add --transport http aeohit https://aeohit.com/mcp --header "Authorization: Bearer YOUR_AEOHIT_API_KEY"

Run it once in a terminal. Add --scope user to use AEOHIT in every project.

Replace YOUR_AEOHIT_API_KEY with a key from Settings → API keys.

Three ways in

Each one uses the same key and does exactly what the app does for your workspace.

  • MCP server

    For AI assistants: https://aeohit.com/mcp speaks the Model Context Protocol over Streamable HTTP. Claude and ChatGPT connect by signing in with AEOHIT; Claude Code, Cursor, VS Code and Windsurf with a key.

  • REST API

    For your own code: JSON over HTTPS at https://aeohit.com/api/v1, described by an OpenAPI 3.1 document you can import into Postman, a ChatGPT action or a client generator.

  • Command line

    For terminals and CI: aeohit check, scan --wait, fix, publish and report --pdf, with --json on every command and exit codes a pipeline can act on. The @aeohit/cli package is being published to npm.

Get a key

Workspace owners and admins create keys. Each key belongs to one workspace.

  1. Sign in to AEOHITNo plan is needed to run free checks; scans, fixes and publishing need one.
  2. Open Settings → API keysName the key after where it will live, such as “Cursor on my laptop”.
  3. Choose read or read and writeRead keys see scores, fixes and reports. Write keys can also add brands, start scans, write fixes and publish them.
  4. Copy it onceWe keep only a fingerprint of it, so it is shown a single time. Revoke it there whenever you like.

Connect from Claude.ai, ChatGPT and other apps

No key to copy: add AEOHIT as a custom connector with the address https://aeohit.com/mcp, sign in with AEOHIT, then choose the workspace and whether the app may only read or also make changes.

  • Claude (claude.ai and the desktop app)

    1. Open Settings → Connectors and choose Add custom connector.
    2. Name it AEOHIT and enter https://aeohit.com/mcp as the URL.
    3. Choose Connect, sign in with AEOHIT, then pick the workspace and the access.

  • ChatGPT

    1. Open Settings → Apps & Connectors and turn on developer mode under Advanced settings.
    2. Create a connector named AEOHIT with https://aeohit.com/mcp as the MCP server URL and OAuth as the authentication.
    3. Sign in with AEOHIT when asked, then pick the workspace and the access.

  • Any MCP client with OAuth

    1. Add a remote (Streamable HTTP) server at https://aeohit.com/mcp without a header.
    2. The client finds AEOHIT’s sign-in on its own (the 401 answer names it) and registers itself.
    3. Approve it in the browser window it opens. Clients without OAuth use an API key instead.

Owners and admins of a workspace can connect apps. Each one appears in Settings → API keys under Connected apps, where you can disconnect it at any time. A connection acts with the access of the person who approved it, and stops if that person is no longer an owner or admin.

What your assistant can do

The MCP server gives your assistant these tools, a latest-report resource per brand and an “improve AI visibility” prompt that walks through check, fixes and publishing.

With any key

  • aeohit_check_businessFree check of a website, or a business by name and city
  • aeohit_list_brandsBrands in your workspace
  • aeohit_get_visibilityScore, trend, engines and share of voice
  • aeohit_list_invisible_questionsQuestions where engines do not name you
  • aeohit_list_competitorsWho engines name instead, with their share
  • aeohit_get_scanA scan’s progress and results
  • aeohit_get_auditThe site audit and its findings
  • aeohit_list_fixesFixes written so far
  • aeohit_get_fixA fix’s content and how to install it

With a write key

  • aeohit_add_brandAdd a brand by its website
  • aeohit_run_scanStart a scan
  • aeohit_generate_fixWrite a fix
  • aeohit_publish_fixPublish a fix to your site (asks you first in most clients)

API reference

Send Authorization: Bearer aeo_live_… (or an access token from signing in) with every request. Errors come back as { ok: false, error, reason, message }. The full contract is in the OpenAPI document.

  • GET/api/v1/meYour workspace, plan and what is left of its allowances
  • POST/api/v1/checkThe free AI-visibility check for a website, or a name and city
  • GET/api/v1/brandsYour brands
  • POST/api/v1/brandsAdd a brand (no scan starts)write key
  • POST/api/v1/brands/{id}/scansStart a scan within your planwrite key
  • GET/api/v1/scans/{id}Progress, then score, engines, competitors and invisible questions
  • GET/api/v1/brands/{id}/dashboardThe dashboard of the latest full scan
  • GET/api/v1/brands/{id}/fixesFixes written for the brand
  • POST/api/v1/brands/{id}/fixesWrite one fix within your monthly allowancewrite key
  • GET/api/v1/fixes/{id}A fix and its content
  • POST/api/v1/fixes/{id}/publishPublish to your connected WordPress sitewrite key
  • GET/api/v1/brands/{id}/auditThe latest site audit and open findings
  • GET/api/v1/reports/{scanId}.pdfA finished scan as a PDF report

Limits, said plainly

API calls use your plan’s allowance. Nothing through a key costs more, or less, than the same thing in the app.

Requests
60 a minute and 1,000 a day per key. Past either, the answer is 429 with a Retry-After header. On Enterprise, 600 a minute and 10,000 a day.
Free checks
20 a day per workspace (200 on Enterprise), shared by its keys, on the same engines as the public check. Repeats within a week return the same report at no cost.
Scans and fixes
Scans spend your plan’s engine runs and fixes count against its monthly allowance, exactly as in the app. Without a plan or trial they answer 402.
Keys
Up to 10 active keys per workspace. A key stops working when it is revoked, or when the person who created it is no longer an owner or admin.
Publishing
Fixes publish to WordPress sites connected through the AEOHIT plugin. Other sites get the fix to install by hand.
Signed-in apps
An app connected by signing in has the same limits as one key, counted per connection. Its access lasts 60 minutes and renews on its own; an app unused for 60 days asks you to sign in again.
Results
AEOHIT measures what AI engines answer and helps improve it. No one can guarantee how an engine will answer.

Start with one key

Create a key, paste one line into your assistant, and ask it how visible your business is.

Create an API keyRun a free check first