Analyze a CSP policy API
Read Content-Security-Policy from a public response or from policy text supplied by the caller. unsafe-inline, unsafe-eval, a script wildcard, and data: scripts are confirmed. This is not a full policy review.
The Analyze a CSP policy operation is part of the Cybersecurity Configuration Intelligence API on BRAINIAC.software. Read Content-Security-Policy from a public response or from policy text supplied by the caller. unsafe-inline, unsafe-eval, a script wildcard, and data: scripts are confirmed. This is not a full policy review. It is exposed as POST /api/v1/security-configuration/csp-policy-analyze and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Public website response Configuration supplied in the request. Limitations: These checks do not show that a website is secure. Only one public GET is sent per supplied URL or path. No exploit, brute force, or credential test is attempted. A path is requested only when the caller lists it. Cookie values are not copied into the response. Private addresses, credential URLs, and non-standard ports are not fetched. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Audit security headers, Audit TLS configuration, Audit cookie attributes, Audit a CORS policy. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/security-configuration/csp-policy-analyzeExample request
curl -i -X POST "https://www.brainiac.software/api/v1/security-configuration/csp-policy-analyze" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"contentSecurityPolicy": "default-src 'self'; script-src 'unsafe-inline' 'unsafe-eval' *"
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Audit security headers — $0.04 USDC
- Audit TLS configuration — $0.04 USDC
- Audit cookie attributes — $0.03 USDC
- Audit a CORS policy — $0.04 USDC
Related APIs
- CVE & Dependency Security API
- Software Supply Chain Security API
- Malware & File Threat Intelligence API
Cybersecurity Configuration Intelligence APIFull docsHow it works