For agent builders

Put a deterministic text-integrity layer around your AI agent.

Language models are good at reasoning over text. They are not the ideal place to perform exact Unicode inspection, secret-pattern detection, or schema validation. ScrubMyText provides those mechanical checks through REST and MCP.

Before model ingestion

Use scan_untrusted_text, detect_secrets, or sanitize_agent_context on webpages, emails, documents, tickets, or retrieved context before it enters the model.

Before an action

Use validate_output to confirm that model-produced JSON satisfies the shape your application expects before a tool or downstream API receives it.

One-call pipeline

Use prepare_for_agent to normalize text, inspect characters, scan risk signals, detect credentials, redact patterns, and return agent-ready text plus a report.

Example workflow

email / webpage / document
          ↓
prepare_for_agent
          ↓
clean context + risk report
          ↓
       AI agent
          ↓
validate_output
          ↓
   downstream action

ScrubMyText intentionally reports signals rather than claiming that text is “safe.” Semantic prompt injection and trust decisions remain the responsibility of the agent application.

Agent-facing tools

Every tool can be called over REST or the remote MCP server.

REST API

https://api.scrubmytext.com

View API docs

Remote MCP

https://api.scrubmytext.com/mcp

Connect via MCP