# Context.dev Brand Prefetch

> Context.dev Brand Prefetch 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-09-13).

Signals to the Context.dev API that brand data for a specific domain will be fetched soon, warming the cache to reduce latency on subsequent calls.

## Facts

- Endpoint: POST https://mpp.orthogonal.com/context-dev/brand/prefetch
- Price: $0.03/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-13
- 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-brand-prefetch-be5f4a35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VdMSibM0YXKAbUYds1qad

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-brand-prefetch-be5f4a35 -d '<json body>'
```

Example prompt: Before we fetch the full brand data for stripe.com, send a prefetch signal to Context.dev so the data is ready and we get a faster response when we actually retrieve it.

## When to prefer this

Use this endpoint immediately before calling any brand data retrieval endpoint (Retrieve, Retrieve Simplified, Fonts, Query, etc.) when minimizing latency is important. Ideal in workflows where you know which domain you'll query next and have a small window to pre-warm the cache. Not useful if you need the actual brand data immediately without a preparatory step.

## Known failure modes

- Invalid or malformed domain returns a 400 error
- Domain cannot be resolved or is inaccessible, prefetch may silently fail or return an error
- Authentication failure if API credentials are missing or invalid
- Rate limiting if too many prefetch signals are sent in rapid succession

## How this service works

Signal that you may fetch brand data for a particular domain soon to improve latency. 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 was received; no brand data is returned. The side effect is that the Context.dev backend begins warming its cache for the specified domain, reducing latency on the subsequent brand data retrieval call.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/context-dev-brand-prefetch-be5f4a35/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)