Score payload anomaly and input safety API
Score a caller-supplied JSON value or text string for nesting depth, mixed types, injection-shaped text, and size inflation. Matching is local and deterministic. The payload is not executed, fetched, or stored.
The Score payload anomaly and input safety operation is part of the Payload Anomaly Scoring API on BRAINIAC.software. Score a caller-supplied JSON value or text string for nesting depth, mixed types, injection-shaped text, and size inflation. Matching is local and deterministic. The payload is not executed, fetched, or stored. It is exposed as POST /api/v1/security/payload-anomaly-score 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: Caller-supplied JSON or text processed locally Limitations: A pattern match is not proof of an exploit, and a high safety score is not a guarantee that the payload is safe. The payload is not parsed by a browser, database, or template engine. No network call is made and nothing is written to disk. Walking stops after a fixed number of values. Later values are reported as not scored. Line numbers are included when the payload is text and the reference occurs once. A JSON object is referenced by path. 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 the other resources on the product page. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/security/payload-anomaly-scoreExample request
curl -i -X POST "https://www.brainiac.software/api/v1/security/payload-anomaly-score" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"payload": {
"user": "ada",
"note": "admin' OR '1'='1",
"profile": {
"bio": "<script>alert(1)</script>",
"meta": {
"a": {
"b": {
"c": {
"d": {
"e": {
"f": {
"g": 1
}
}
}
}
}
}
}
},
"flags": [
1,
"1",
true
],
"filter": {
"$gt": 0
}
}
}
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.