AI Security Guard - Security Scanning for Autonomous AI Agents
https://aisecurityguard.io/v1/skillAgents process inputs they don't control: APIs, MCP tools, documents, web content, emails. Each is a potential attack surface. A February 2026 zero-click RCE via calendar invite proved even routine inputs can compromise agents. Five specialized detection experts analyze content before your agent processes it: pattern detection, intent drift analysis, semantic analysis, structure analysis, and code analysis across 8 languages. Covers prompt injection, credential exfiltration, data theft, code injection, social engineering, and 60+ attack patterns. POST /v1/guard with content + intent_contract. Returns verdict, confidence, findings, recommendations. Agent decides: proceed, constrain, escalate, or block. Privacy by design: No API keys (x402 cryptographic payments). Content deleted in 15 minutes. No training on customer data. Zero data retention on AI provider. Services: Content scanning ($0.0015-$0.024), Document analysis (PDF/DOCX), Preflight validation (~10ms), Follow-up Q&A ($0.0125), Security advisory ($0.01). Payment via USDC on Base/Ethereum. Endpoints: /v1/guard, /v1/guard/quote, /v1/document/scan, /v1/guard/preflight, /v1/qa, /v1/advisory https://aisecurityguard.io/v1/skill
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 121ms · p95 323msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/22/2026, 12:00:00 AM | 100% | 1 | 109ms |
| 7/23/2026, 12:00:00 AM | 100% | 1 | 113ms |
| 7/24/2026, 12:00:00 AM | 100% | 1 | 110ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 71ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 139ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 115ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 79ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 123ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 185ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 87ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 79ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 86ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 130ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 25ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 1098ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 173ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 98ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 77ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 142ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 196ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 74ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 109ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 117ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 154ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 125ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 98ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 124ms |
| 8/18/2026, 12:00:00 AM | 100% | 8 | 104ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 103ms |
| 8/20/2026, 12:00:00 AM | 100% | 13 | 132ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- DIGITALOCEAN-104-248-0-0
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
Response schema
{}