Cactus
heycactus.ai
· Cactus
Answers a team's questions about its own product from its code, its help pages and its customer conversations, for a member of the team signed in with OAuth. Every message is answered on its own. Cactus's own help answers anyone, with no sign-in, at https://mcp.heycactus.ai/p/cactus/a2a; its card is https://cactus.heycactus.ai/.well-known/agent-card.json.
heycactus.ai via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
D
Conformance score: 52/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Card history
1 snapshot Every change toagent-card.json
| Captured | Hash | Snapshot |
|---|---|---|
| 2026-10-18 23:51:44 current | a14536d05958… |
view → |
Endpoints
| Agent card | https://heycactus.ai/.well-known/agent-card.json |
| Provider | https://heycactus.ai |
| Docs | https://heycactus.ai/auth.md |
Skills · 1 declared by this agent
These skills are declared by the agent. A taxonomy link appears only when we can classify a skill confidently.
Send a question about one of your team's products as text. The reply is one answer drawn from everything the team can see, with the pages it cites and a link to…
Health · last 1 probes
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/heycactus.ai) [](https://agenstry.com/agents/heycactus.ai) [](https://agenstry.com/agents/heycactus.ai) [](https://agenstry.com/agents/heycactus.ai)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "Cactus",
"description": "Answers a team's questions about its own product from its code, its help pages and its customer conversations, for a member of the team signed in with OAuth. Every message is answered on its own. Cactus's own help answers anyone, with no sign-in, at https://mcp.heycactus.ai/p/cactus/a2a; its card is https://cactus.heycactus.ai/.well-known/agent-card.json.",
"version": "1.0.0",
"supportedInterfaces": [
{
"url": "https://heycactus.ai/a2a",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
},
{
"url": "https://mcp.heycactus.ai/a2a",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
}
],
"provider": {
"organization": "Cactus",
"url": "https://heycactus.ai"
},
"documentationUrl": "https://heycactus.ai/auth.md",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false
},
"securitySchemes": {
"cactus": {
"oauth2SecurityScheme": {
"description": "Sign in to Cactus as a member of the team.",
"flows": {
"authorizationCode": {
"authorizationUrl": "https://heycactus.ai/oauth/authorize",
"tokenUrl": "https://heycactus.ai/oauth/token",
"scopes": {
"cactus:read": "Read your team's pages, code map and past conversations",
"cactus:ask": "Ask Cactus questions and start investigations; each creates a conversation"
}
}
},
"oauth2MetadataUrl": "https://heycactus.ai/.well-known/oauth-authorization-server"
}
}
},
"securityRequirements": [
{
"schemes": {
"cactus": {
"list": [
"cactus:ask"
]
}
}
}
],
"defaultInputModes": [
"text/plain"
],
"defaultOutputModes": [
"text/markdown",
"application/json"
],
"skills": [
{
"id": "ask-team-product",
"name": "Ask about your product",
"description": "Send a question about one of your team's products as text. The reply is one answer drawn from everything the team can see, with the pages it cites and a link to the conversation in Cactus. A team with more than one product names it by ref in the request's metadata.product. An answer that takes longer than a few minutes comes back as that link, where it is written when it is done.",
"tags": [
"product",
"code",
"support",
"changelog"
],
"examples": [
"What changed in our product this week?",
"Which of our help pages explain billing?",
"What have customers asked about the new release?"
]
}
]
}