Your AI agent can now read the Vigilbase docs

More of the questions people ask about Vigilbase now go to an AI assistant first. "How do I create an organisation API key in One?" "What does the Agent API return when I run out of scans?" An agent that answers from memory can be out of date or simply wrong.

So we've made the docs something an agent can look things up in. From today, any script or MCP client can search docs.vigilbase.com and read a whole page before it answers.

Two ways in

The Docs API lives at https://api.vigilbase.com/docs/v1, on the same API host as the Tools and One APIs. It has two operations:

• GET/search?q=… returns the pages that contain every word you asked for, best match first. When the match is under a heading, the link goes straight to that heading.
• GET/pages?path=… returns one page as Markdown, with every link made absolute.

$ curl -s 'https://api.vigilbase.com/docs/v1/search?q=api+keys&limit=2'
{
  "results": [
    {
      "path": "tools/developers/api-keys",
      "title": "API keys",
      "description": "Create a free developer API key in Vigilbase One to raise the Agent API rate limit, and keep it safe.",
      "url": "https://docs.vigilbase.com/tools/developers/api-keys",
      "markdownUrl": "https://docs.vigilbase.com/tools/developers/api-keys.md"
    },
    {
      "path": "one/api",
      "title": "Vigilbase One API",
      "description": "Calling the Vigilbase One API on api.vigilbase.com/one/v1 and one.vigilbase.com/api, with sign-in, API keys, pagination, rate limits and errors.",
      "url": "https://docs.vigilbase.com/one/api#organisation-api-keys",
      "markdownUrl": "https://docs.vigilbase.com/one/api.md",
      "heading": {
        "id": "organisation-api-keys",
        "text": "Organisation API keys"
      }
    }
  ]
}

The MCP server at https://mcp.vigilbase.com now has two more tools:

They sit next to the public security tools that were already there: run_security_headers, run_email_security, get_security_badge and list_security_tools. Add the server to your MCP client once, and your agent can check a site's headers and then read how to fix what it found, in the same conversation.

No account, no key

Neither needs a Vigilbase account or an API key. The Docs API allows 60 requests a minute per client IP, sends standard RateLimit headers, and answers a 429 with Retry-After when you go over. Any website can call it from a browser.

Errors use the same application/problem+json format as the rest of api.vigilbase.com, so a client built for the Tools or One API already knows how to read them. The OpenAPI document is at https://api.vigilbase.com/docs/v1/openapi.json.

Built on the same contract as our other APIs

The Docs API is defined in the same code-defined contract as the Tools and One APIs. That one definition generates its OpenAPI document and its entry in the api.vigilbase.com catalogue. The MCP tools call the same API rather than a copy of the search, so the website, the API and your agent all get the same results.

It joins what was already there for agents: every docs page has a Markdown copy at its URL plus .md, every page is listed in docs.vigilbase.com/llms.txt, and you can ask Vigil from any docs page.

Try it

Add https://mcp.vigilbase.com to your MCP client as a remote server and ask it something about Vigilbase. The MCP server guide has the setup steps, and the Docs API reference has every parameter and error.