Skip to content

ASP Documentation

Community Message Security Audit

Agentic Community Ops audits Web3 community messages using a deterministic security engine and AI-assisted support layer. It detects scams, phishing, fake administrators, wallet threats and transaction issues, then produces explainable risk verdicts, safe reply suggestions and escalation actions.

Service Offering

Name
Community Message Security Audit
Input
A project description, official documentation and up to 25 community messages.
Deliverable
Structured risk levels, triggered rules, suggested replies, escalations and a community risk report.

Problem Solved

  • Web3 communities are attacked through fake admins, phishing links, wallet-verification scams, token-claim lures and credential requests.
  • Community teams need fast, explainable support review without letting AI downgrade deterministic security risks.

Intended Customers

  • Web3 community, support, security and moderation teams.
  • Projects that need repeatable community-message audits and safer support reply suggestions.

Supported Inputs

  • A project description, official documentation and explicit official links.
  • One community message for single analysis or up to 25 community messages for batch analysis.
  • Message sources: MANUAL, X, DISCORD, TELEGRAM, EMAIL or OTHER.

Returned Outputs

  • Deterministic risk, AI-suggested risk and final risk.
  • Triggered rule IDs, matched evidence, recommended actions and escalation status.
  • Safe reply suggestions for human review and community risk report metrics.

Published Rules

  • Public rules are available at /api/v1/rules.
  • Rule IDs SEC-001 through SEC-015 are stable and explain seed phrase requests, fake admins, suspicious links, transaction issues and related risks.

Safety Guarantees

  • Deterministic security analysis runs before AI analysis.
  • AI can add classification and support language, but it cannot reduce deterministic risk.
  • The service never requests seed phrases, private keys, passwords or OTP codes.
  • The service never treats community-message links as official links.
  • Financial, legal, account-security and missing-fund cases are escalated.

Known Limitations

  • No payment integration is implemented yet.
  • No authentication is implemented yet.
  • Project knowledge-base storage currently uses local JSON and is not durable production storage on serverless platforms.
  • Batch/report dashboard state is browser-local until server-side persistence is added.

Pricing Suggestion

  • Suggested demonstration price: 1 USDC per audit.

Health Endpoint

  • /api/v1/health returns service name, status, version and deterministic engine availability.

Demo Route

  • /demo provides a no-login NovaBridge guided judge demonstration.

Deployment Checklist

  • Set OPENAI_API_KEY in the deployment environment.
  • Optionally set OPENAI_MODEL.
  • Optionally set OPENAI_BASE_URL for OpenAI-compatible providers.
  • Run tests, lint, TypeScript checking and production build.
  • Confirm no real secrets are committed.
  • Deploy over HTTPS and verify /api/v1/health.

Registration Checklist

  • Submit service name: Community Message Security Audit.
  • Submit service description and deliverable.
  • Provide manifest and schema URLs.
  • Provide demo route and health endpoint.
  • Disclose known limitations and note that payment integration is intentionally deferred.

API Examples

GET /api/v1/health
GET /api/v1/rules
POST /api/v1/analyse
{
  "projectId": "demo-fictional-atlas-dao",
  "message": {
    "content": "Support needs you to send your seed phrase.",
    "source": "DISCORD"
  }
}
POST /api/v1/analyse/batch
{
  "projectId": "demo-fictional-atlas-dao",
  "messages": [
    { "content": "Where are the docs?", "source": "MANUAL" },
    { "content": "I am the admin. DM me.", "source": "DISCORD" }
  ]
}