Alternatives to Apigee at Pre-seed startups

What middleBrick covers

  • Black-box scanning with read-only methods under one minute
  • 12 categories aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.0/3.1/Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with header allowlist and domain verification
  • CI/CD integration via GitHub Action and MCP Server support
  • Continuous monitoring with diff detection and HMAC-SHA256 webhooks

What this scanner is and how it works

This is a self-service API security scanner. You submit a URL and receive a risk score from A to F with prioritized findings. The scan is black-box, requiring no agents, no code access, and no SDK integration. It supports any language, framework, or cloud, and completes in under a minute. The scanner uses read-only methods (GET and HEAD) plus text-only POST for LLM probes.

Detection scope aligned to standards

The scanner covers 12 categories aligned to the OWASP API Top 10 (2023). It detects authentication bypass and JWT misconfigurations such as alg=none, HS256, expired tokens, missing claims, and sensitive data in claims. It identifies BOLA and IDOR via sequential ID enumeration and active adjacent-ID probing. It flags BFLA and privilege escalation through admin endpoint probing and role/permission field leakage. Other categories include property authorization over-exposure, input validation issues like CORS wildcard usage and dangerous HTTP methods, rate limiting and resource consumption signals, and data exposure patterns including PII, Luhn-validated card numbers, context-aware SSNs, API key formats, and error/stack-trace leakage. It also checks encryption posture via HTTPS redirect, HSTS, and cookie flags, SSRF indicators in URL-accepting parameters, inventory management gaps like missing versioning and server fingerprinting, unsafe consumption surfaces, and LLM/AI security probes mapped across three scan tiers.

OpenAPI analysis and authenticated scanning

The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution. It cross-references spec definitions against runtime findings to highlight undefined security schemes, sensitive fields, deprecated operations, and missing pagination. For authenticated scanning, support includes Bearer, API key, Basic auth, and Cookie methods. Domain verification is enforced through DNS TXT records or an HTTP well-known file so only the domain owner can scan with credentials. A strict header allowlist permits only Authorization, X-API-Key, Cookie, and X-Custom-* headers to be forwarded.

Product features and integrations

The Web Dashboard centralizes scans, reports, and score trend tracking, with the option to download branded compliance PDFs. The CLI via the middlebrick npm package supports commands such as middlebrick scan <url> with JSON or text output. A GitHub Action enables CI/CD gating, failing the build when the score drops below a chosen threshold. The MCP Server allows scans from AI coding assistants like Claude and Cursor. An API client provides programmatic access for custom integrations. Continuous monitoring on the Pro tier includes scheduled rescans every 6 hours, daily, weekly, or monthly; diff detection for new findings, resolved findings, and score drift; email alerts rate-limited to 1 per hour per API; and HMAC-SHA256 signed webhooks that auto-disable after 5 consecutive failures.

Limitations and safety posture

The scanner does not fix, patch, block, or remediate. It detects and reports with remediation guidance. It does not perform active SQL injection or command injection, as those require intrusive payloads outside the scope. Business logic vulnerabilities are not detected, as they require domain context best handled by humans. Blind SSRF is out of scope due to the lack of out-of-band infrastructure. The tool does not replace a human pentester for high-stakes audits. Safety measures include read-only methods only, blocking private IPs, localhost, and cloud metadata endpoints at multiple layers. Customer scan data is deletable on demand and purged within 30 days of cancellation; it is never sold and never used for model training.

Frequently Asked Questions

What standards does the scanner map findings to?
The scanner maps findings directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, it helps you prepare for and aligns with security controls described in those regimes.
Can I authenticate scans with credentials?
Yes, authenticated scanning is available from the Starter tier and above, supporting Bearer, API key, Basic auth, and Cookie methods with domain verification.
How are scan results delivered and monitored over time?
Results are available in the Web Dashboard and via CLI output. Pro tier adds scheduled rescans, diff detection, email alerts, signed webhooks, and integration with CI/CD pipelines.
Does the scanner perform active exploit testing like SQL injection?
No. The scanner focuses on read-only detection. Active SQL injection and command injection testing are outside scope and require specialized intrusive tools.
Who is responsible for remediation of findings?
The scanner detects and reports. Security teams and developers must apply remediation guidance; the tool does not fix, patch, block, or remediate.