Detect BEC patterns API
Detect Business Email Compromise patterns such as payment-change language, executive persona cues, external Reply-To, and lookalike sender domains from supplied mail.
The Detect BEC patterns operation is part of the Email & Communication Security API on BRAINIAC.software. Detect Business Email Compromise patterns such as payment-change language, executive persona cues, external Reply-To, and lookalike sender domains from supplied mail. It is exposed as POST /api/v1/email-security/bec-pattern-detect and priced at $0.05 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 raw email, EML, headers, attachments, URLs, and conversation copies Public DNS TXT when publicDns is requested Public HTTP(S) redirect follows when followPublicUrls is requested Limitations: Messages are never sent and mailboxes are never logged into. Email and attachment bytes are never uploaded to external malware or sandbox scanners. Observed facts are separated from inferred threats. Indicators are not labeled confirmed malicious without sufficient evidence. Optional public DNS and URL follows are limited to public hosts with strict SSRF protections. Missing authentication or DNS evidence is reported as missing, not invented. 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 Analyze email headers, Detect email spoofing indicators, Detect phishing signals, Check domain impersonation. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/email-security/bec-pattern-detectExample request
curl -i -X POST "https://www.brainiac.software/api/v1/email-security/bec-pattern-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",
"brandDomains": [
"acme.example"
],
"companyNames": [
"Acme"
],
"emails": [
{
"id": "M1",
"from": "\"Acme CFO\" <cfo@acme-examp1e.example>",
"replyTo": "payments@attacker.example",
"subject": "Urgent payment",
"bodyText": "Please process a wire transfer today and keep this confidential.",
"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
- Analyze email headers — $0.04 USDC
- Detect email spoofing indicators — $0.05 USDC
- Detect phishing signals — $0.04 USDC
- Check domain impersonation — $0.03 USDC