Detect suspicious order patterns API

Compare supplied amounts with a Tukey fence when 8 orders share a currency, and with a customer's own median when that customer has at least four amounts. A new address counts only after earlier orders. One signal is an indicator, not confirmed fraud.

The Detect suspicious order patterns operation is part of the E-commerce Fraud & Order Risk API on BRAINIAC.software. Compare supplied amounts with a Tukey fence when 8 orders share a currency, and with a customer's own median when that customer has at least four amounts. A new address counts only after earlier orders. One signal is an indicator, not confirmed fraud. It is exposed as POST /api/v1/ecommerce-fraud/suspicious-order-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: Order history supplied in the request. Limitations: Patterns are calculated only from the orders in the request. One signal is an indicator, not a finding that a customer is fraudulent. No payment is processed, no order is blocked, and no merchant account is accessed. A full card number is not copied. A statistical outlier is not confirmed fraud. 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 Detect card-testing patterns, Detect bulk-order patterns, Detect refund patterns, Detect promotion patterns. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/ecommerce-fraud/suspicious-order-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/ecommerce-fraud/suspicious-order-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "orders": [
    {
      "id": "O-1",
      "customer": "C-1",
      "created": "2026-11-01",
      "amount": 20,
      "currency": "USD",
      "status": "paid",
      "address": "1 Main St, 10001",
      "country": "US",
      "billCountry": "US"
    },
    {
      "id": "O-2",
      "customer": "C-1",
      "created": "2026-11-02",
      "amount": 22,
      "currency": "USD",
      "status": "paid",
      "address": "1 Main St, 10001",
      "country": "US",
      "billCountry": "US"
    },
    {
      "id": "O-3",
      "customer": "C-1",
      "created": "2026-11-03",
      "amount": 21,
      "currency": "USD",
      "status": "paid",
      "address": "1 Main St, 10001",
      "country": "US",
      "billCountry": "US"
    },
    {
      "id": "O-4",
      "customer": "C-1",
      "created": "2026-11-04",
      "amount": 400,
      "currency": "USD",
      "status": "paid",
      "address": "9 Other St, 20002",
      "country": "US",
      "billCountry": "CA"
    },
    {
      "id": "O-5",
      "customer": "C-2",
      "created": "2026-11-01",
      "amount": 19,
      "currency": "USD",
      "status": "paid",
      "country": "US",
      "billCountry": "US"
    },
    {
      "id": "O-6",
      "customer": "C-3",
      "created": "2026-11-01",
      "amount": 23,
      "currency": "USD",
      "status": "paid",
      "country": "US",
      "billCountry": "GB"
    },
    {
      "id": "O-7",
      "customer": "C-4",
      "created": "2026-11-01",
      "amount": 18,
      "currency": "USD",
      "status": "paid",
      "country": "US",
      "billCountry": "US"
    },
    {
      "id": "O-8",
      "customer": "C-5",
      "created": "2026-11-01",
      "amount": 20,
      "currency": "USD",
      "status": "paid",
      "country": "US",
      "billCountry": "US"
    }
  ]
}
JSON

An 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 APIs

E-commerce Fraud & Order Risk APIFull docsHow it works