# Context.dev Prefetch Brand Data by Email

> Context.dev Prefetch Brand Data by Email is a paid API for AI agents from Context.dev at mpp.orthogonal.com, paid per call via MPP, $0.03/call, status unknown (last checked 2026-10-11).

Signals to the server that brand data for a domain associated with a given email address will be needed soon, pre-warming the cache to reduce latency on the subsequent fetch.

## Facts

- Endpoint: POST https://mpp.orthogonal.com/context-dev/brand/prefetch-by-email?utm_source=zero.xyz
- Price: $0.03/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Provider: Context.dev
- Docs: https://www.context.dev
- Website: https://www.context.dev
- Tags: scraping, brand, context, extraction, web, data
- Canonical page: https://www.zero.xyz/c/context-dev-prefetch-brand-data-by-email-fa5e4190
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E5v5IK00H07yIpRED7Pio

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 context-dev-prefetch-brand-data-by-email-fa5e4190 -d '<json body>'
```

Example prompt: Before I fetch brand details for john.doe@acme.com, prefetch the brand data for that email so the actual retrieval is faster.

## When to prefer this

Use this endpoint when you know you will shortly call 'Retrieve By Email' and want to minimize the latency of that subsequent call. It is a performance hint, not a data retrieval endpoint — choose it only as a preparatory step before an email-based brand lookup, not as a standalone data source.

## Known failure modes

- Invalid or malformed email address returns a 400 Bad Request
- Disposable or free email domain may not have meaningful brand data to prefetch
- Network timeout if the upstream scraping pipeline is overloaded
- Rate limiting if too many prefetch signals are sent in quick succession
- 404 or service error if the domain extracted from the email cannot be resolved

## 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 prefetch signal has been received and the server has begun warming the brand data cache for the domain associated with the provided email address. No brand data is returned directly; this call primes the system for a faster subsequent Retrieve By Email call.

## More

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