Detect failed-delivery patterns API

Group supplied failed, undeliverable, refused, or returned orders by postcode, address, or carrier. A pattern needs at least three orders. One failure is not a carrier finding.

The Detect failed-delivery patterns operation is part of the Returns & Delivery Intelligence API on BRAINIAC.software. Group supplied failed, undeliverable, refused, or returned orders by postcode, address, or carrier. A pattern needs at least three orders. One failure is not a carrier finding. It is exposed as POST /api/v1/returns-delivery/failed-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: Orders, addresses, events, and rates supplied in the request. Limitations: Records are copied only from labeled fields in the request. No carrier tracking event is added. An address check does not confirm that a carrier can deliver. A return cost and a return window come only from supplied rates and day counts. No carrier account is contacted and no return is initiated. 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 Classify delivery exceptions, Validate shipping-address structure, Calculate return shipping cost, Analyze return reasons. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/returns-delivery/failed-pattern-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/returns-delivery/failed-pattern-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "orders": [
    {
      "id": "O-1",
      "status": "failed",
      "carrier": "Example Carrier",
      "postcode": "SW1A 1AA",
      "country": "GB"
    },
    {
      "id": "O-2",
      "status": "failed",
      "carrier": "Example Carrier",
      "postcode": "SW1A 1AA",
      "country": "GB"
    },
    {
      "id": "O-3",
      "status": "failed",
      "carrier": "Example Carrier",
      "postcode": "SW1A 1AA",
      "country": "GB"
    },
    {
      "id": "O-4",
      "status": "delayed",
      "carrier": "Example Carrier",
      "postcode": "SW1A 1AA",
      "country": "GB"
    }
  ]
}
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

Returns & Delivery Intelligence APIFull docsHow it works