# Email Local Part Brand Impersonation Bulk Check

> Email Local Part Brand Impersonation Bulk Check is a paid API for AI agents from email.intel.rallylive.ca, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-18).

Checks up to 20 email addresses at once for brand impersonation in the local part (the portion before the @), returning per-item results concurrently with a failure count.

## Facts

- Endpoint: GET https://email.intel.rallylive.ca/bulk/email/local-part/brand-impersonation
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/email-local-part-brand-impersonation-bulk-check-63b39d79
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__RhCLiBrnY0C-art0ZDMt

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability email-local-part-brand-impersonation-bulk-check-63b39d79
```

Example prompt: I have a list of 15 email addresses from our sign-up form — can you run all of them through the brand impersonation check on the local part and tell me which ones look like they're spoofing a known brand, along with any that failed?

## When to prefer this

Choose this endpoint when you have 2–20 email addresses to check for local-part brand impersonation and want to minimize API calls and latency via concurrent batch processing. It is preferable to calling the single endpoint in a loop, as it processes all items concurrently and returns results in input order. If you have more than 20 emails, split them into batches of 20. Use the single endpoint only when you need to check exactly one address and want the simplest possible call.

## Known failure modes

- Input list exceeds 20 emails — batch limit exceeded error
- Malformed email address in the list causes a per-item error with that item's error field populated
- All items fail processing — failure count equals input count with no successful results
- Empty input list returns no results
- Network timeout during concurrent processing may result in partial results with elevated failure count

## How this service works

Bulk email local part brand impersonation: up to 20 emails in one call, processed concurrently, results in input order with a per-item error field and a failure count. Same answer per item as the single endpoint. Batch enrichment for agents that hold a list. $0.10 per batch.

## Output

An ordered array of per-item results matching the input list, each containing the same answer as the single-item endpoint (impersonation verdict and relevant details), plus a per-item error field for failed checks and a top-level failure count indicating how many items could not be processed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/email-local-part-brand-impersonation-bulk-check-63b39d79/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from email.intel.rallylive.ca](https://www.zero.xyz/host/email.intel.rallylive.ca/llms.txt)