# Qonoro Address Normalize

> Qonoro Address Normalize is a paid API for AI agents from api.qonoro.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-16).

Parses a raw postal address string into structured components (number, street, city, state, ZIP) and returns a USPS-formatted normalized output with confidence score.

## Facts

- Endpoint: POST https://api.qonoro.ai/v1/address/normalize
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/qonoro-address-normalize-7d895cc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3-tefTIYiYQJGw1ZhRw8n

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 qonoro-address-normalize-7d895cc0 -d '<json body>'
```

Example prompt: Can you parse and normalize this address into structured components — street number, street, city, state, and ZIP — and give me the USPS-formatted version: '123 main st apt 4b new york ny 10001'?

## When to prefer this

Choose this endpoint when you need to parse and normalize a single US (or supported country) postal address string into structured components at sub-second latency, especially in agentic workflows requiring USPS-standard output with confidence scoring. Prefer it over geocoding APIs when you need address component decomposition rather than lat/lng coordinates, and over batch file processing services when you need real-time per-address normalization with x402 micropayment billing.

## Known failure modes

- Unparseable address input returns low confidence score or null normalized field
- Non-US address without country code may fail or return incomplete components
- Malformed or completely garbled input may return null normalized output with parse_notes explaining the issue
- Missing required 'address' field returns a validation error
- Ambiguous abbreviations or incomplete addresses may yield lower confidence scores

## How this service works

Parse and normalize postal addresses into structured components. Returns address number, street, city, state, ZIP, and USPS-formatted output. Postal address parsing and normalization. Sub-second. x402-native.

## Output

Returns a JSON object containing parsed address components (house number, street, city, state, ZIP, etc.), a USPS-formatted normalized address string, a confidence score (0–1), address type classification, optional parse notes, cache hit flag, request ID, and response time in milliseconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "Raw postal address to normalize."
  },
  "country": {
   "type": "string",
   "description": "ISO 3166-1 alpha-2 country code (default: 'US')."
  },
  "buyer_region": {
   "type": "string",
   "description": "Optional privacy-safe buyer region."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/qonoro-address-normalize-7d895cc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.qonoro.ai](https://www.zero.xyz/host/api.qonoro.ai/llms.txt)