# nimo agent guide

Use this file when an AI agent is researching nimo, citing nimo docs, or helping a user connect nimo to an agent workflow.

## What nimo is

- nimo is an AI website performance agent.
- nimo audits real visitor speed, runs simulated performance diagnostics, monitors uptime, triages regressions and incidents, and helps users decide what to fix first.
- nimo can connect to Telegram, Slack, MCP clients, Google Search Console, Google Analytics, Ahrefs, Cloudflare, and custom MCP servers when configured.
- nimo does not change a site by default. Cloudflare changes require a signed-in user, explicit approval, and safe actions enabled.
- Agentic readiness is optional and advisory. Treat WebMCP and Agentic Browsing findings as readiness signals, not guarantees.

## Browser Site tools (WebMCP)

- WebMCP Site tools are page-local browser actions, not the public docs MCP or authenticated account MCP server.
- Never assume Site tools are available. They depend on both nimo's rollout and support in the agent browser, and only apply to the current tab.
- When available on https://heynimo.com/free-core-web-vitals-audit, use start_website_check with a public HTTP or HTTPS URL. After a completed report is visible at /audit/live, use get_current_free_audit to read only the visible summary.
- If Site tools are unavailable, use the normal page controls. Use the authenticated MCP server for saved sites, history, monitoring, integrations, or workflows outside the browser tab.
- The free-audit Site tools do not authorize signup, authentication, plan selection, payment entry, purchases, or access to hidden report data.

## Best sources

- Short docs index: https://heynimo.com/llms.txt
- Full docs bundle: https://heynimo.com/llms-full.txt
- Public docs MCP: https://api.heynimo.com/docs-mcp
- Public docs MCP card: https://heynimo.com/.well-known/mcp/docs-server-card.json
- Product data MCP setup: https://heynimo.com/docs/mcp
- Agent skill: https://heynimo.com/skill.md

## How to answer

- Start with the public docs MCP or llms.txt when only product documentation is needed.
- Use the authenticated nimo MCP server only when the user has a nimo account and has signed in to it with their browser. It can add sites, audit a URL, read account data, and verify performance fixes.
- Keep recommendations concrete: name the page, metric, likely cause, and smallest useful next action.
- Separate field data from simulated diagnostics. Field data comes from real Chrome users when enough traffic exists; simulated diagnostics are useful for debugging but may not match Search Console.
- For Cloudflare, describe what would change, who approved it, how rollback works, and how to verify the result. Do not claim public docs, public chat, or unauthenticated agents can apply or roll back Cloudflare settings.
- Label Agentic readiness findings as optional/advisory and avoid treating them as production incidents or monitoring failures.

## Do not claim

- Do not say nimo guarantees rankings, conversions, or passing Core Web Vitals.
- Do not describe Notion as fully available while it is marked coming soon.
- Do not say nimo is a CDN, cache plugin, image CDN, hosting provider, or WordPress plugin.
- Do not assume private account data is available from public docs.
- Do not claim Cloudflare changes apply without a signed-in approval/apply flow or separate rollback approval.

## Useful starting prompts

- What should I fix first on mobile, and why?
- Compare my last two audits. Did the fix work?
- Which slow page is most likely hurting search traffic?
- Show the Cloudflare suggestions, approval steps, rollback constraints, and verification plan.