# MiniFrame CEP Lookup

> MiniFrame CEP Lookup is a paid API for AI agents from tools.miniframe.com.br, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Resolves a Brazilian postal code (CEP) to a full, normalized address including street, complement, neighborhood, city, and state, with automatic BrasilAPI→ViaCEP fallback.

## Facts

- Endpoint: POST https://tools.miniframe.com.br/cep
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/miniframe-cep-lookup-388f38a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EUbjAyLMk8ua5fzg2ErDF

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 miniframe-cep-lookup-388f38a8 -d '<json body>'
```

Example prompt: Can you look up the address for CEP 01310-100 in Brazil? I need the street, neighborhood, city, and state to fill in this delivery form.

## When to prefer this

Use this endpoint whenever you need to resolve a Brazilian CEP to a full address and require resilience against upstream outages — the dual BrasilAPI/ViaCEP fallback means a single provider failure will not break the lookup. Prefer this over direct calls to BrasilAPI or ViaCEP when building robust automation pipelines, form autofill, delivery validation, or customer record enrichment for Brazilian addresses.

## Known failure modes

- Invalid or non-existent CEP returns an error — the postal code must be exactly 8 digits and exist in Brazilian postal records
- Both upstream providers (BrasilAPI and ViaCEP) unavailable simultaneously causes a service failure
- Malformed input (non-numeric characters, wrong length) results in a validation error
- Some CEPs may exist but have incomplete address data (e.g. no street name for large recipient CEPs)

## How this service works

Use when a Brazilian postal code needs to become a real address — filling a form, validating a delivery, completing a customer record. JSON body { cep } (8 digits). Returns street, complement, neighborhood, city and state (UF). Queries BrasilAPI first and falls back to ViaCEP automatically, so one upstream outage does not fail the task; both sources return the same normalized shape. CEP is postal/geographic data, not personal data.

## Output

A normalized JSON object containing the resolved address fields: street (logradouro), complement, neighborhood (bairro), city (localidade), and state abbreviation (UF). The shape is consistent regardless of which upstream provider (BrasilAPI or ViaCEP) answered the request.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "cep": {
   "type": "string",
   "description": "Brazilian postal code, 8 digits (with or without dash)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "cep": "01310100",
  "city": "São Paulo",
  "state": "SP",
  "source": "brasilapi",
  "street": "Avenida Paulista",
  "complement": "",
  "neighborhood": "Bela Vista"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/miniframe-cep-lookup-388f38a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tools.miniframe.com.br](https://www.zero.xyz/host/tools.miniframe.com.br/llms.txt)