Project assistant

The Assistant answers questions about the project you have open, such as “which pages lost the most positions since last month?” or “what are the critical issues from the last audit?”.

What it can read

The assistant answers by calling read-only tools over the project’s stored data, the same tools the MCP server offers:

• audits, their issues and crawled pages;
• saved keywords and tags;
• rank trackers, latest positions, trends, the position matrix and each keyword’s history;
• stored backlink snapshots;
• the project’s context: brief, competitors, key pages and research log;
• the workspace’s credit balance and plan.

Three rules hold for every answer:

• Every number comes from a tool. If no tool returns it, the assistant says the project does not store it instead of guessing.
• It never buys a lookup. It cannot run a keyword search, a rank check or an audit, so asking a question never triggers a data purchase.
• It sees one project. Questions about another project have to be asked from inside that project.

What a question costs

A turn is charged for the model calls it makes. Before it starts, netweft holds the most one turn can cost, 223 credits: up to 5 model calls, each with a full prompt and a full answer. A question the assistant answers straight away settles for a fraction of that. If a turn fails partway, it is charged for the model calls that ran.

Conversations

Each conversation is private to the person who started it. The assistant reads the last 20 messages of a conversation as its memory, so start a new conversation when you change topic. Your conversations lists earlier ones to reopen.

An archived project keeps its conversations readable, but the assistant does not answer new questions until the project is restored.