epovest.com

List the trackers of the account, current versions: configuration, status, keywords, analysts, project and the recalculated cost per survey.

Create a tracker in draft.

Update the configuration of a tracker: only the fields you send change.

Start or restart the measurement of a tracker against the prepaid credit balance.

Run one survey of a measuring tracker right now, on top of its schedule.

Pause the measurement of an active tracker.

File a finished tracker away: a campaign that ended, a brand that was sold, a trial that is over.

The projects of the account: the folders trackers are filed under (one project per tracker at most; pure organization, no effect on measurement or billing).

Create a project to file trackers under: one project per BRAND, never per language.

Correct the name of a project: the folder keeps its id, its canon, its trackers, its surfaces and its logbook, and the name shown is the only thing that changes.

The brand canon of a project and every revision it went through.

Revise the brand canon of a project.

The addresses of the brand that a watched page can link to.

Set the addresses of the brand that are neither its canonical website nor a page of the surface registry: a satellite domain the customer does not want to keep aligned, a tracking link, a partner page.

File a project away once the folder has served its purpose: a client that left, a brand that was sold.

The surface registry of a project: the pages about the brand where the customer has the FINAL SAY (website, GitHub, LinkedIn, X, YouTube, Wikidata, directories, app stores...).

Register a surface of a project: one page about the brand where the customer has the final say (their site, their profiles, their listings, wherever they can change the content).

Update the registry sheet of a surface: only the fields you send change (a sent languages list replaces the previous one; an empty label or notes clears it).

Record what a surface actually carries, cell by cell, as many moves as you want in one call.

Add a check of your own to the checklist of one surface: a requirement the person holds on THAT page, in their words.

Correct a check of your own on a surface: its label, and whether it restates the canon.

Take a check of your own out of the checklist of a surface: it leaves the list, stops holding the page short of aligned and stops accepting ticks.

Bring a check of your own back to the checklist of a surface, with the cells it had: it becomes work again, so the page needs it verified to count as aligned.

Take a surface out of the registry: the page stops being followed, and the registry stops asking to bring it in phase with the canon.

Bring a surface back to the registry, with its sheet and its alignment journal as they were.

Move the page to the corroboration registry: someone else has the final say on it (the customer lost, or never had, the hand on the content).

The corroborations recorded for a project: the pages about the brand where someone else has the FINAL SAY, each with its exact address, the source it sits on (domain), the publication date when known, and free notes.

Record a page about the brand where someone else has the final say.

Update the sheet of a corroboration: only the fields you send change (an empty label goes back to the derived one, an empty notes or published_on clears it).

Record that the page is no longer there (article unpublished, link dead), or put it back live with archived false.

Read the page again and report what it says today.

Move the page to the surface registry: the customer has, or takes, the final say on it (their own profile or listing recorded on the wrong side, or a source that became a reliable channel).

The MENTIONS a search engine has shown the brand in, found in the text the engine itself returned next to each address.

Refuse a suggested page: it is never proposed again for this project.

The logbook of a project, newest first: every dated move, composed from two sources.

Record an action in the logbook of a project: what was done, and WHEN it was done.

Edit a manual logbook entry: only the fields you send change (empty notes clear them).

Take a manual logbook entry out of the logbook, and the annotation it placed on the curves with it.

Bring an entry back to the logbook, with the annotation it placed on the curves.

What there is to do for the GEO work, and where to resume it.

Add a quest to the file of a project: a next move the customer decided, kept where the work resumes ("get our MCP server listed on the AI tool directories").

Edit a quest: only the fields you send change (empty notes clear them).

Mark a quest done: the move happened.

Set a quest aside: the customer decided the move is off.

Put a closed quest back in the file: it returns among the open moves with its sheet as it was, the date it was added, its author and its notes, so a quest closed by mistake or taken up again keeps its own history.

The score series of a tracker: one row per analyst, keyword, engine, tracker version and survey period, in chronological order.

The raw answers of ONE AI engine for a tracker, newest surveys first, paginated.

The keyword suggestions DISCOVERED on a tracker: domains the surveyed engines cite as sources again and again, that no tracked keyword covers.

Accept one discovered suggestion (domain) or a batch (domains): each becomes a tracked keyword of the tracker, in place, and its series starts at the next survey.

Dismiss one discovered suggestion (domain) or a batch (domains): the domains are never proposed again on this tracker, and appear in the dismissed list until restored.

Restore one dismissed domain (domain) or a batch (domains): it leaves the tracker dismissed list and becomes eligible for discovery again, suggested anew while the engines keep citing it (accepting it stays a distinct move).

The competitor scans of the account, newest first: a basket of up to 5 companies of one market, asked to one engine, from which the scan returns THE PLACES that corroborate them.

One scan and its list of PLACES: the domains the engine cited while answering about the basket, ranked by how many of its companies each place covers (`subjects`, the number that carries the tool) then by AI Authority.

Prepare a competitor scan on a basket of up to 5 companies of the same market.

Arm a prepared scan: the engine is asked, and the prepaid balance is debited by the amount `estimated_cost_minor` announced on the scan.

Correct a scan still in draft, and set the cadence of one already armed.

The Atlas: the sources the AIs cite when they answer YOUR trackers.

One entry of the Atlas, read by its id: the domain and its AI Authority on each AI.

The channels behind one source of the Atlas: who published the videos the AIs cited when answering the questions of this account, with their videos and the questions that surfaced each one.

The settings of the account: the legal name, billing country, postal address and intra-EU VAT number printed on its invoices, plus the language we write to it in and the time zone its hours are shown in.

Change the settings of the account.

The prepaid credit balance of the account: available credits, which never expire, and the amount reserved by surveys in progress with the detail of each reservation.

What the account SPENDS: one call, three answers, and they must never be mixed up.

Prepare a top-up of the prepaid credit balance and return the hosted payment link.

Send a message to the humans behind Epovest: report a problem, suggest an improvement, ask a question.

The support threads of the account, most recent first: what was asked, and whether the support team has answered.

One support thread with its messages, including the answers of the support team.