# BloodHound by WarHoundAI: our security agent

> BloodHound is the larger, more powerful security product WarHound AI is developing. Mini Hound is the smaller public version you can use now for read-only checks of public website code.

Official source: https://warhoundai.com/bloodhound/
Updated: 2026-11-03

## Want to try something now?

Mini Hound is live with Free and Plus plans. It reviews public website code, explains possible issues, and supports follow-up questions.

BloodHound is the larger product in development. Continuous monitoring, broader assessments and automatic code changes are not included in Mini Hound.

- [Open Mini Hound](https://warhoundai.com/mini-hound/app/)
- [Mini Hound details](https://warhoundai.com/mini-hound/)

## BloodHound at a glance

BloodHound is being built for developers who need to understand how their application behaves beyond the happy path. Its intended role is to investigate exposed application surfaces, connect related observations, and turn supported findings into work a developer can review. This page explains the product direction in detail and separates planned capabilities from what is available today.

Product status as of 1 November 2026

| Area | Current status |
| --- | --- |
| Public product information and educational guides | Available without an account |
| Account registration, email verification and sign-in | Available; verified accounts can open Mini Hound |
| BloodHound security assessments | Mini Hound is live with Free and Plus plans. Web chat and entitled customer API and private MCP access are available. Broader BloodHound assessments, monitoring and editor extensions remain in development. |
| Continuous monitoring and developer integrations | Planned; not publicly available |
| Pricing | Free and one-month Plus token access available; manual renewal |
| Private research prototype | Public-source collection and AI-assisted review, restricted to internal administration |

- [Create an account](https://warhoundai.com/sign-up/)
- [Read the company’s security approach](https://warhoundai.com/security/)
- [Full product status](https://warhoundai.com/product-status/)
- [Subscription pricing](https://warhoundai.com/pricing/)

## What is BloodHound?

BloodHound is the name of WarHoundAI's first autonomous application security agent. It is being designed to investigate a website's public attack surface, probe defenses within an authorized scope, and help explain security weaknesses and possible fixes.

BloodHound is an agent product in development, not a newly released foundation model. Mini Hound currently uses Mercury 3 through Inception Labs. The larger BloodHound product's release model configuration and performance have not been announced. No proprietary model weights or training methods are claimed.

Mini Hound is WarHound AI’s live security agent. BloodHound is our larger product in development.

## Planned security testing capabilities

The product direction combines several related review areas. These are intended capabilities, not a validated coverage list or a guarantee that BloodHound detects every weakness in these categories. The checks that can be performed will depend on the authorized scope, available application context and integrations released at launch.

What BloodHound is being designed to investigate

| Capability | Application question | Useful evidence |
| --- | --- | --- |
| Attack-surface discovery | Which pages, routes and APIs are reachable within scope? | An inventory tied to the authorized target |
| Exposed secrets | Does public client code or configuration reveal a private credential? | A redacted location and enough context to review the exposure |
| Authentication and access control | Can an actor perform an operation outside its intended permissions? | Controlled identities, an expected rule and a sanitized observation |
| API and tenant boundaries | Does each operation enforce the user’s access to a particular record or workspace? | Both allowed and denied cases using synthetic records |
| Configuration and CORS | Do exposed settings permit behavior beyond the application’s requirements? | The affected endpoint, response behavior and prerequisites |
| Rate limits and abuse controls | Can a sensitive or expensive action be repeated beyond its intended limits? | Bounded observations within agreed request and safety limits |
| Remediation guidance | What should change, and how will the owner verify the correction? | A proposed fix, uncertainty, ownership and retest criteria |

- [API authorization testing and a worked example](https://warhoundai.com/blog/api-authorization-testing-saas/)
- [Handling exposed API keys](https://warhoundai.com/blog/protect-api-keys-ai-built-apps/)

## How the planned BloodHound workflow works

1. Establish permission and scope. The application owner identifies the approved domains, environments, accounts, operations and safety limits. A website URL alone is not proof of ownership. The intended assessment must stay within that agreement.

2. Build application context. Discovery is intended to identify relevant public pages, routes and APIs. Where released integrations make code or configuration available, that context could inform the investigation; a URL-only workflow should not be assumed to include private source-code access.

3. Plan an investigation. The agent is intended to use the context to identify questions about exposed secrets, authentication, permissions and configuration. A suspected issue is a hypothesis to investigate, not automatically a confirmed vulnerability.

4. Perform bounded checks. The intended workflow tests relevant behavior within the permitted scope. Permission boundaries need controlled identities and appropriate test fixtures. Actions with side effects, costly jobs or sensitive data need explicit limits.

5. Review findings and uncertainty. The goal is to connect an observation to the affected operation, expected rule, prerequisites and practical impact. Findings should distinguish confirmed evidence from untested possibilities, and mask secrets rather than reproduce them in reports.

6. Remediate and retest. Suggested fixes are intended to support a human review. An owner should confirm the deployed correction blocks the forbidden action while preserving legitimate use. A proposed patch, a merged change and a verified deployed fix are different states.

- [Define an authorized assessment scope](https://warhoundai.com/blog/authorized-security-testing-scope/)
- [Download the scope worksheet](https://warhoundai.com/guides/assessment-scope-template.md)

## The planned security workflow

The planned workflow brings discovery, testing, and remediation together. A developer starts with a website URL or a supported integration, defines what may be tested, and reviews findings with context and suggested next steps.

- Discover: map the application's publicly reachable pages, routes, APIs, and other exposed surfaces within the agreed scope.
- Test: investigate potential exposed secrets, access-control and authentication gaps, misconfigurations, permissive CORS, and missing rate limits.
- Remediate: review vulnerability details, severity, supporting context, and actionable guidance. Suggested fixes should be reviewed by the application's owner before use.

## Why an agent-driven approach?

A fixed check can be useful when the failure pattern is already known. Application weaknesses can also depend on relationships: who the user is, which workspace owns a record, what an operation changes, and whether a related endpoint enforces the same rule. BloodHound’s intended agent workflow uses that context to guide multi-step investigation rather than treating each response as an isolated result.

This does not remove the need for ordinary engineering controls, dependency review, trusted authorization logic, human judgment or independent testing. WarHoundAI has not published comparative detection results showing that BloodHound outperforms another tool. The goal is a connected investigation and remediation workflow, not a claim of complete or infallible security.

- [Agentic security testing versus conventional scanning](https://warhoundai.com/blog/agentic-security-testing-vs-scanning/)

## Who BloodHound is being built for

Independent developers and startups: review the security implications of a working web application before making it available to customers. The intended focus is practical findings and fixes that a small team can understand.

Teams building with AI coding tools: investigate server-side permissions, exposed configuration and application behavior that a polished generated interface does not establish. AI-built code still needs the same trust boundaries as other software.

SaaS engineering teams: examine how authentication, tenant membership, record access and API operations fit together. A useful result should explain which rule was tested and which related paths remain unreviewed.

Developer platforms and AI tool builders: use the planned API or assistant integrations to bring assessment requests and structured findings into an existing workflow. Private MCP and customer public-source review API access are available to entitled accounts; the broader assessment API and a public SDK remain planned.

- [Security checklist for AI-built applications](https://warhoundai.com/blog/security-checklist-ai-built-apps/)
- [Guides you can use before BloodHound launches](https://warhoundai.com/guides/)

## An illustrative investigation: a workspace permission gap

Imagine a staging document service with two disposable workspaces. Alice belongs to Workspace A and Bob belongs to Workspace B. The policy permits each member to read documents only from their own workspace. This is an educational scenario, not a BloodHound scan or a claim about a real application.

A useful investigation first confirms legitimate reads. It then checks a known synthetic Workspace A document using Bob’s own test session. If the hypothetical endpoint returns that document, the observation points to a missing resource or tenant permission check. A valid login would not make the cross-workspace access acceptable.

The intended report would explain the endpoint, permission rule, controlled identities, sanitized evidence and confirmed impact. The correction belongs in the trusted authorization or data-access layer. A meaningful retest would verify that cross-workspace access is denied and both legitimate reads still work.

The example shows the reasoning and evidence a developer needs. It does not promise that BloodHound can currently execute this workflow, assign a universally correct severity, or test every related operation automatically.

- [Read the full authorization example and test matrix](https://warhoundai.com/blog/api-authorization-testing-saas/#worked-example)
- [See the paired finding and retest example](https://warhoundai.com/blog/actionable-security-findings-remediation/#worked-example)

## What a useful security finding should contain

The planned reporting direction is structured, reviewable evidence. A finding should identify the affected operation and environment, the actor’s permissions, the expected behavior, the observation and its limits. A vulnerability label or screenshot alone is often insufficient to decide what to fix.

Remediation guidance should describe the rule to enforce, identify assumptions and explain how to retest. Generated suggestions still need review for the application’s real roles, transaction boundaries and deployment environment. The exact BloodHound report format, export formats and API response schema have not been published.

- A specific title and affected application surface.
- Reproduction prerequisites and the expected permission or configuration rule.
- Minimal, sanitized evidence with secret values masked.
- Confirmed impact separated from uncertainty and untested paths.
- Practical remediation guidance and an owner for follow-up.
- The deployed version and both allowed and denied retest cases.

- [Write actionable security findings](https://warhoundai.com/blog/actionable-security-findings-remediation/)
- [Download a human-review finding worksheet](https://warhoundai.com/guides/security-finding-template.md)

## Planned integrations

These are planned integrations for the larger BloodHound product. Mini Hound web chat is already live; it is separate from the planned BloodHound assessment integrations.

- MCP: bring security context and natural-language assessment workflows into a compatible AI assistant using the Model Context Protocol.
- Editor plugin: review project code, configuration, and application routes alongside findings and suggested fixes.
- API: trigger assessments programmatically and retrieve structured findings for a platform or backend.
- Chat: share an authorized website URL, explore findings, and ask follow-up questions about remediation.
- Browser extension: explore a website-oriented workflow for requesting security checks from the browser.

## Security capabilities for developer products

Mini Hound provides a customer review API and a private MCP for compatible clients with an active API entitlement. Use your account’s API key; creating a key does not activate a plan or bypass website verification.

The larger BloodHound assessment API remains in development. Visit your API keys page for current Mini Hound access.

## Continuous monitoring is part of the product direction

Applications change as routes, dependencies, configuration and permissions evolve. BloodHound’s planned continuous monitoring direction is intended to help teams revisit security questions as their application changes, rather than relying solely on a manually initiated assessment.

Monitoring is not currently available. WarHoundAI has not published a schedule, event trigger, supported change source, alert channel or response-time commitment. Continuous monitoring should not be interpreted as a promise of real-time prevention, incident response or automatic blocking of attacks.

## Authorized and controlled testing

Security testing is intended only for applications you own or have explicit permission to test. Assessments should have a defined scope and safety limits. Finding a public website does not grant permission to test it.

WarHoundAI describes a security-first product direction with careful handling of customer data, limited access, masking of detected secrets, and minimal exposure of credentials. Product safeguards, third-party analysis providers, retention rules, and deletion controls will need to be documented as those workflows launch. No independent security certification or compliance certification is claimed here.

## Coverage limits and human review

No assessment can establish complete application security. Coverage depends on the target, available roles, test data, scope restrictions and the evidence a tool can collect. An inaccessible private workflow or a missing test identity can leave important behavior unreviewed. Findings can also require human validation.

BloodHound is not presented as a replacement for secure design, code review, dependency management, incident response, or a compliance audit. WarHoundAI has not published independent performance benchmarks, security certifications or a service-level agreement. Any future coverage or assurance claim needs evidence specific to the released product.

Programming-language support, frameworks, code-host integrations and deployment-platform compatibility have not been finalized publicly. Product previews should not be used as a compatibility matrix.

## Current availability and previews

The public website, email-and-password account registration, email verification, and sign-in are available. Creating an account or saving a project URL does not start a security assessment or verify ownership of that target.

An internal prototype is operational in the private admin environment: bounded public HTTPS resource collection, source organization, AI-assisted review and evidence-linked candidate findings. It has been tested against synthetic fixtures. It is not the public BloodHound assessment service; ordinary accounts do not gain administrative access.

BloodHound assessments and continuous monitoring remain in development. Mini Hound web chat is launched. Private MCP and customer review API access are operational for entitled accounts with verified websites. Editor plugins and browser extensions are not available.

Example audit requests, response payloads, findings, vulnerability counts, editor screens, and chat conversations are illustrative product previews. Example targets use reserved example domains. They are not real scans of visitor applications or evidence that a particular third-party application is vulnerable.

No launch date, supported-language matrix, independently validated detection benchmarks, or service-level agreement is published. Public product descriptions distinguish the available website and accounts from features still in development.

- [Current product status and prototype evidence](https://warhoundai.com/product-status/)

## Pricing

Mini Hound Free is $0/month with a separate ₹2 activation fee. Plus is $4.99 USD for one month, with manual renewal. Token allowances and Google Cloud Gemini routing are live. Choose a plan and complete checkout before using Mini Hound.

- [View the plans and business model](https://warhoundai.com/pricing/)

## Website data and privacy

The website uses accounts and secure sessions for access to private workspaces. Website analytics records page visits, IP addresses, approximate location, browser and device information, and referrer information for up to 90 days. Analytics respects browser Do Not Track and Global Privacy Control opt-outs. Visitor records are restricted to administrators.

Public product information can be read without an account. Private accounts, administration pages, verification links, and application API responses are not public product documentation. Do not submit passwords, authentication codes, API keys, or other confidential information when asking about the product.

## Start using Mini Hound

Create an account, verify your email, activate Free or Plus at checkout, then verify your website to start using Mini Hound.

Use the guides and worksheets to plan the scope and prepare non-sensitive code examples.

- [Create your account](https://warhoundai.com/sign-up/)
- [Sign in to an existing account](https://warhoundai.com/sign-in/)
- [Explore the security guides and templates](https://warhoundai.com/guides/)
- [Ask a product question](https://warhoundai.com/contact/)

## What is WarHoundAI?

WarHound AI builds application security tools for developers, startups and engineering teams. Mini Hound is the live product for reviewing public website code, understanding possible issues and keeping source evidence.

BloodHound is the larger security product in development.

## Developer security guides and review templates

Start with our public guides for reviewing AI-built applications, permissions, private credentials, and AI tool integrations. The examples and editable worksheets can be used independently of BloodHound; they do not represent a live assessment or a released integration.

- [Application security guides and review templates](https://warhoundai.com/guides/)
- [MCP security integration review](https://warhoundai.com/guides/mcp-security/)