# Docs > How to use netweft, page by page: projects, keyword research, rank tracking, site audits, backlinks, credits, team, API keys and MCP. Source: https://netweft.com/docs How to use netweft, page by page, in reading order. Every doc is also available as markdown at the same path plus `.md`. - [Quickstart: from sign-in to your first rank check](https://netweft.com/docs/quickstart) (Getting started): Sign in with Google, GitHub or an email address, choose a plan to start its trial, then answer six onboarding steps. You finish with a project, saved keywords and a rank tracker that checks them weekly. - [Plans and trials](https://netweft.com/docs/plans-and-trials) (Getting started): Every workspace needs one of three plans: Pro, Studio or Agency. Each starts with a free trial and trial credits, bills monthly or yearly, and sets the limits on projects, keywords and audits. - [Projects and markets](https://netweft.com/docs/projects-and-markets) (Getting started): A project is one site: a domain and the market its keywords are measured in. netweft has keyword data for 143 countries; 49 of them come without keyword difficulty and search intent. - [Keyword research](https://netweft.com/docs/keyword-research) (Research): Enter a seed keyword and get up to 200 ideas in one lookup, each with search volume, keyword difficulty, cost per click and intent, measured in the project's market. Open any idea to see the live results page. - [Domain overview](https://netweft.com/docs/domain-overview) (Research): Name a domain and netweft reports its domain rank, organic keyword count, estimated monthly visits and their value, with three paid lists behind it: ranking keywords, pages and keyword ideas. - [Backlinks](https://netweft.com/docs/backlinks) (Research): Name a domain to see its live backlinks, referring domains and most linked pages. Every lookup stores a snapshot, and the History tab charts how the totals moved between them. - [Saved keywords and tags](https://netweft.com/docs/saved-keywords-and-tags) (My site): Saved keywords are the list the rest of a project works from. Tag them to group them, refresh their volume and difficulty when the market moves, and export the list as CSV. - [Rank tracking](https://netweft.com/docs/rank-tracking) (My site): A tracker checks where a domain ranks for a list of keywords, daily, weekly, monthly or on demand, on desktop, mobile or both. Every position is stored with the time it was seen, and a check's price depends on its depth. - [Site audit](https://netweft.com/docs/site-audit) (My site): A site audit crawls up to the plan's page limit from one start URL, obeys robots.txt, and ranks 25 kinds of problem as critical, warning or info. Page speed is an opt-in Lighthouse measurement on up to 10 pages. - [Search performance](https://netweft.com/docs/search-performance) (My site): Search performance shows a project's own Google data: Search Console queries and pages with clicks, impressions, CTR and position, and Analytics sessions, active users and key events. Reading it costs no credits. - [AI visibility](https://netweft.com/docs/ai-visibility) (My site): AI visibility counts the AI answers that name the project's domain on Google or ChatGPT, how often those answers are asked for, which pages they cite, and how the domain's mentions compare with its competitors'. - [Project assistant](https://netweft.com/docs/project-assistant) (Assistant and context): The assistant answers questions about one project from the data netweft already stores. Every figure it quotes comes from a read-only tool, it never spends credits on a lookup, and a turn costs only the model calls it makes. - [Project context](https://netweft.com/docs/project-context) (Assistant and context): Project context is the brief an agent reads before working on a project: four written sections, a competitor list, key pages with their roles, and an append-only research log. - [Credits and billing](https://netweft.com/docs/credits-and-billing) (Account): One credit is $0.0001 of data-vendor cost. A lookup holds its most likely ceiling before it runs and is charged what the vendor actually billed, never more. Plan credits expire monthly; bought credits never expire. - [Team and roles](https://netweft.com/docs/team-and-roles) (Account): A workspace has three roles. Members read everything and work in projects; admins also manage projects, billing, keys and people; owners can do all of that and hand out the owner role. - [API keys](https://netweft.com/docs/api-keys) (Account): An API key lets an agent read a workspace through the MCP server. Keys belong to the workspace, are shown once, read only what their scopes allow, and can never change data or spend credits. - [MCP server](https://netweft.com/docs/mcp-server) (Developers): netweft runs a Model Context Protocol server at https://api.netweft.com/mcp. An agent with an API key gets 25 read-only tools over the workspace's stored data, and clients that only run local servers connect through netweft-mcp on npm. - [HTTP API](https://netweft.com/docs/http-api) (Developers): Every dashboard screen runs on a documented HTTP API at https://api.netweft.com, described by an OpenAPI 3.1 document. It authenticates with a signed-in session; agents should use the MCP server instead.