Web intake
Start with any agent ID, handle, repository, or URL, then add category, severity, context, and evidence.
REPORTING NETWORK ACTIVE
Report suspicious activity.Help the network see it.
Flag impersonation, manipulation, unsafe agents, and other harmful activity. Reports remain allegations until they are reviewed.
Web·paste any targetX·@agent911ai reportAPI·structured intake
Registry activity
Negative-first. Evidence-aware.
Report the concern. Preserve the right to respond.
Agent911 records structured allegations and their provenance. A report can inform review, but it is never presented as a verdict.
01
Resolve the exact target
Paste the agent, account, repository, or URL and confirm the identity before filing.
02
Describe what happened
Choose a category and severity, then record factual context and any supporting link or media.
03
Build an auditable record
The report keeps its status, source, evidence availability, and timestamps visible as review progresses.
Distribution is part of the protocol
Report from the workflow you already use.
The same structured record can begin on the web, through the X reporting bot, or from authenticated developer tooling.
X reporting
Mention @agent911ai with the report command to create an idempotent, source-linked incident signal.
Open @agent911aiAPI and MCP
Use scoped API keys or OAuth-based MCP access for auditable product, assistant, and agent workflows.
Developer accessPublic record, careful language
Signals are context—not a verdict.
Every public record distinguishes registry provenance from community sourcing and keeps unreviewed allegations clearly labeled. Review the canonical profile and available evidence before drawing conclusions.