# Orthogonal Brand Prefetch by Email

> Orthogonal Brand Prefetch by Email is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Accepts a business email address, extracts and validates the domain, and queues it for brand data prefetching to reduce latency on future brand lookups.

## Facts

- Endpoint: POST https://x402.orthogonal.com/context-dev/brand/prefetch-by-email
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orthogonal-brand-prefetch-by-email-19cf06fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TOCsoJ2RR2XpXA4pHSV4d

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 orthogonal-brand-prefetch-by-email-19cf06fa -d '<json body>'
```

Example prompt: Before we look up brand data for Acme Corp, prefetch the brand info for john.smith@acmecorp.com so the actual lookup is faster.

## When to prefer this

Use this endpoint when you know you will soon need brand data for a specific business domain and want to reduce latency on that future call. It is ideal for pipelines where email addresses are collected ahead of a brand enrichment step, such as CRM imports, lead generation flows, or onboarding sequences. Do not use this to actually retrieve brand data — use the corresponding brand lookup endpoint for that. Also do not use this for consumer or disposable email domains.

## Known failure modes

- Free email provider domain (gmail.com, yahoo.com, etc.) submitted — rejected with an error indicating the domain is not allowed
- Disposable email address detected — rejected with validation error
- Invalid or malformed email address format — returns validation error
- Timeout exceeded (timeoutMS threshold hit) — returns 408 status
- Request made without a paid plan — returns authorization or payment required error

## How this service works

Signal that you may fetch brand data for a particular domain soon to improve latency. This endpoint accepts an email address, extracts the domain from it, validates that it's not a disposable or free email provider, and queues the domain for prefetching. This endpoint does not charge credits and is available for paid customers to optimize future requests. [You must be on a paid plan to use this endpoint]

## Output

A confirmation that the domain extracted from the provided email has been queued for brand data prefetching. The endpoint does not return brand data itself — it signals to the system to pre-load that data so subsequent brand lookups for the same domain complete faster. No credits are charged for this call (though a paid plan is required).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "description": "Email address to prefetch brand data for. The domain will be extracted from the email. Free email providers (gmail.com, yahoo.com, etc.) and disposable email addresses are not allowed."
  },
  "timeoutMS": {
   "type": "integer",
   "description": "Optional timeout in milliseconds for the request. If the request takes longer than this value, it will be aborted with a 408 status code. Maximum allowed value is 300000ms (5 minutes)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orthogonal-brand-prefetch-by-email-19cf06fa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)