Connect your AI to Amaware.

The brand, its plan and limits, how many prompts are tracked and how much room is left, which engines run, the time zone, the last run and the credit balance. Call this first.

How often the brand is named, cited and named first across the answers in a window, with share of voice against the tracked competitors. With include_trend, the daily line and engine health too.

Every prompt on the list with its latest result per engine (named, cited, missed, position), the 28-day spark, asks a month on Pro and up, and how many open actions it feeds. Filter by active, stage, engine or a search word.

One prompt with the latest answer per engine: whether the brand was named, its position, every brand the answer named, the sources it cited with their channel, what the engine searched for, and an excerpt of the answer. Plus the 28-day history per engine.

Prompts where at least one engine did not name the brand in its latest answer, with who was named instead. The shortest route to what to fix.

The domains and pages the engines cite on your prompts, classified by channel (owned, competitor, listicle, review site, community, video, editorial), and which of your own pages get cited, with the 28-day movement.

Every competitor with its domain, aliases, chart colour and share of voice in the window, next to yours.

What to publish next, highest leverage first: each row says what to make (a page, a video, a reply, an email), where it goes, why the engines will pick it up and how many prompts it covers. Defaults to open items; pass a status for completed or skipped ones.

One item on the list with everything behind it: the prompts it covers, the engines that miss, the pages cited instead, the competitors involved, the leverage factors, and whether a brief, a draft or a published URL exists.

The last calls made on this workspace through any key or connection: the tool, when, whether it worked, and the credits it used. Read it before repeating work another agent already did.

This manifest: every tool, what it reads and writes, its inputs, its credits and whether it is available on the caller's plan and balance, plus what an agent cannot do here and why.

Adds prompts to the list and starts tracking them on the next run. Dedupes against what is already tracked and stops at the plan's prompt limit with the exact line the app shows, so a 50-prompt plan never gets a 51st.

Changes a prompt's text or stage. The old row is paused and linked so its history stays on the chart; the new one runs on the next scoped run.

Pauses a prompt (it keeps its history and stops counting against the plan) or tracks it again.

Removes a prompt for good. Pass a reason (not our buyer, wrong product, too broad, wrong competitor, we already rank) and the next suggestions steer away from it. Ask the person before calling this.

Runs one prompt on the workspace's engines right now and returns whether the brand was named and cited and the sources each answer used. Pass a prompt id, or text to add and run a new prompt (the plan's limit applies).

Twenty manual runs a day per workspace.

Prompts the brand can get named for, built from its site, the market's measured demand and what competitors already win, each with a reason sentence. Nothing is added; pass the ones the person keeps to add_prompts.

Charged per prompt returned; the shortfall is refunded.

Tracks a competitor by name and domain, with optional aliases and a chart colour. Takes the lowest free chart slot; twelve is the cap.

Changes a competitor's name, domain, aliases or chart colour. Pass color null to go back to the series colour.

Stops tracking a competitor. Its past mentions stay in the stored answers. Ask the person before calling this.

Changes the brand's name, the aliases the engines might use for it, the domains you own (the main domain always stays), the voice rules briefs follow, the five phrases you want to be the answer for, and the market.

The voice every brief is written in: the one-line pitch, tone words, first person, sentence length, words to use and avoid, sample lines from the site, the two asks and the disclosure line for replies.

Changes any of the voice fields. Send only the fields to change; the rest stay. Every brief from then on uses the new voice.

Reads the brand's site again and rewrites the voice fields from it. Three reads a day; free of credits.

Sets which engines run daily. Every paid plan runs three of the five; pass the full list you want on.

Recomputes the ranked list from the stored answers (the Refresh button). Free; refuses while a run is still going.

Moves an item to new, in progress, completed or skipped (with a reason: not relevant, already exists, no capacity).

Records that the page for an action is live at a URL. Amaware widens your owned domains for a new subdomain, queues the affected prompts, and watches the daily answers for the first citation. With Google Search Console or Bing Webmaster Tools connected, the page is sent to them two hours later and checked daily until it is indexed. Ask the person before calling it.

The finished kit for one action: the exact title tag, meta description, URL, headings, FAQ and schema for a page; the script, title, description and chapters for a video; the reply and disclosure for a thread; the email for a list owner or a writer. Returned as Markdown and as fields, in the brand's own voice. The first request starts writing it (about a minute) and returns status "writing" with retry_in seconds; call again after that and the kit comes back, cached from then on. Write the piece from it exactly, then ask the person to publish and call mark_published.

Credits are charged on the first generation only; reading a cached brief is free. While status is "writing", wait retry_in seconds and call again.

Throws the cached brief away and starts a fresh one, charged like a first brief. Returns status "writing" with retry_in; call get_brief after that many seconds for the new kit. Use it when the evidence changed or the person asked for a different angle.

Two briefs a day for one action.

Edits an existing brief: send kit fields to merge over the stored kit (the Markdown is re-rendered), or brief_markdown to replace the text as is. Use it after the person asks for a different title, angle or FAQ.

Stores the article, post, script, reply or email you wrote from the brief on the action, with the URL once it is live, so the person sees it in the app and other agents do not write it twice. Publishing stays with your own connected tools.

The draft saved on an action, who saved it and when, and its URL if it was published.

What is left in the workspace's credit pool, the allowance, the reset date, what used credits this period, the last twenty ledger rows and the packs on sale.

A Stripe Checkout link for a top-up pack (small, medium or large). Nothing is charged until the person finishes paying; the credits land the moment they do and never expire. Give the link to the person; never pretend the purchase happened.

How many people search each phrase a month on Google and ask it of AI assistants, with difficulty, intent and a twelve-month trend.

The phrases buyers in a category actually search, grown from a few seeds, each with volume, AI volume, difficulty and intent.

The phrases a domain ranks for on Google, with its position, the ranking page and the demand behind each.

The phrases a competitor ranks for and your brand does not, with their position and the demand.

The phrases where Google's AI Overview cites a page on a domain, with the cited page. Defaults to your brand.

The domains and brands that AI answers mention for a topic or a brand, with how often, from a large sample of real prompts on ChatGPT and Google's AI Overview.

Samples cover ChatGPT and Google AI Overview, US and English.

The real prompts whose AI answers name a brand, each with the sources the answer cited. Sources and counts only, never the answer text.