Detect extension/format mismatches API
Identify mismatches between caller-supplied filenames/extensions and local magic-byte formats, including double extensions.
The Detect extension/format mismatches operation is part of the Malware & File Threat Intelligence API on BRAINIAC.software. Identify mismatches between caller-supplied filenames/extensions and local magic-byte formats, including double extensions. It is exposed as POST /api/v1/file-security/file-extension-mismatch-detect and priced at $0.03 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 files, hashes, and analysis reports processed locally Limitations: Uploaded files and scripts are never executed and are never sent to external malware scanners. Static pattern matches are not confirmed malware verdicts; absence of matches is not malware-free. Archive inspection applies strict depth, entry-count, and decompression limits. Observed facts are separated from inferred threat hypotheses. No paid threat-intel feed is used and no API key is required. 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 Extract file behaviour indicators, Cluster malware artifacts, Analyze executable metadata, Detect macro document risk. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/file-security/file-extension-mismatch-detectExample request
curl -i -X POST "https://www.brainiac.software/api/v1/file-security/file-extension-mismatch-detect" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"asOf": "2026-11-04T21:00:00.000Z",
"files": [
{
"id": "X1",
"filename": "invoice.pdf.exe",
"fileBase64": "TVoAAGZha2UtcGU=",
"source": "Caller-supplied"
}
]
}
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
- Extract file behaviour indicators — $0.04 USDC
- Cluster malware artifacts — $0.04 USDC
- Analyze executable metadata — $0.04 USDC
- Detect macro document risk — $0.04 USDC