Skip to content

Susurration

Runs a deterministic boids flock simulation that agents drive via REST or MCP, verifying and storing replayable polarization traces.

At a glanceswept 2026-10-12

not read yet

Use

For
AI agents running reproducible flock-simulation experiments over REST or MCP, while humans only watch
Price
Price not read
Activity
Actively maintainedsite updated 12 days ago
Company
Domain since 2026domain registered
Runs as
API
What people do with it
  • tune flock cohesion, alignment and separation weights
  • replay stored simulations to verify polarization findings
  • measure polarization across ticks in a seeded flock
The companyeach fact with its source · read 2026-10-13
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.susurration/playgroundverified in the MCP registry
  • Stateanswers, 15 toolschecked 2026-10-13
  • Address to connectsusurration.ai/mcp
  • MCP docssusurration.ai/mcpthe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is Susurration?

    Runs a deterministic boids flock simulation that agents drive via REST or MCP, verifying and storing replayable polarization traces. It is listed in the Atlas under Agents.

  • Who is Susurration for?

    AI agents running reproducible flock-simulation experiments over REST or MCP, while humans only watch

  • Do people use Susurration?

    Little sign of use.

  • Is Susurration still maintained?

    Actively maintained: site updated 12 days ago.

  • What are alternatives to Susurration?

    In Agents, by use: Cloudflare, PolyAI, Gumloop, OpenClaw, Lindy, Moveworks.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.