Use Hivekind with your agent
Public website helpers prepare URLs for your review. Connect MCP to work with your authenticated Hivekind workspace.
Public website helpers
These GET endpoints require no authentication. They return a canonical URL and a next step. You choose when to start a diagnostic or scan, submit a form, or email a report.
- Prepare a HiveICP check. Validate a public company domain and return a prefilled HiveICP page for the user to review. This capability does not run the diagnostic or submit personal information.
GET /.well-known/agent-capabilities/hiveicp?domain=example.com - Prepare a HiveScan. Validate a public company domain and return a prefilled HiveScan page for the user to review. This capability does not run a scan, unlock a report, or submit personal information.
GET /.well-known/agent-capabilities/hivescan?domain=example.com - Navigate to a public Hivekind experience. Return a canonical URL for approved public product, MCP, pricing, blog, compare, use-cases, guides, glossary, research, resources, news, HiveEvents, or demo-request content. This capability does not submit forms or start scans.
GET /.well-known/agent-capabilities/navigation?destination=pricing
For domain helpers, supply a public domain or HTTP(S) URL without credentials or custom ports. Invalid inputs return 400. Helpers do not fetch the supplied website or execute paid work.
Browser tools
Browsers supporting WebMCP can discover the same three helpers while this site is open. Each tool returns a prepared URL. It does not navigate, start scans, or submit information. Other browsers can use the GET endpoints above.
Connect your workspace through MCP
Add https://api-v2.hive-loop.com/mcp as a Streamable HTTP MCP connection, complete OAuth, and authorize the intended workspace.
- Canonical protected-resource metadata
- Canonical authorization-server metadata
- MCP connection and domain guides
MCP and its OAuth issuer are hosted on api-v2.hive-loop.com. The marketing site's OAuth well-known paths redirect to that API. Clients must use the API issuer and resource identifiers. An unauthenticated MCP request returns 401 with a metadata pointer; connect through OAuth to continue.