# Business Change Intelligence API – Location Timeline

> Business Change Intelligence API – Location Timeline is a paid API for AI agents from api.businesschanges.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Retrieves a chronological list of business-change events for a specific address or building, returning match scope metadata and suite-level identity.

## Facts

- Endpoint: POST https://api.businesschanges.dev/v1/locations/timeline
- 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/business-change-intelligence-api-location-timeline-d2da34eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2arAd1Z9WKzfAcHGbts1z

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 business-change-intelligence-api-location-timeline-d2da34eb -d '<json body>'
```

Example prompt: Pull the full business-change timeline for 450 Mission Street, San Francisco, CA — match on the exact premise and give me up to 100 events.

## When to prefer this

Choose this endpoint when you need the full ordered history of business-change events at a specific address or building, especially when suite-level identity matters. It is the right choice for due diligence, tenant history research, sales prospecting on location activity, or any workflow that needs paginated chronological event data tied to a physical premises. Use the sibling delta-feed endpoint instead if you only need changes since a prior sync point.

## Known failure modes

- Address not found or unresolvable — returns empty event list or 404
- Invalid UUID format for locationId — returns 400 validation error
- matchScope 'building' requested without sufficient address specificity — may return broader or no results
- cursor value expired or malformed — returns 400 or restarts pagination
- Limit exceeds 100 — returns 400 validation error
- regionCode or city missing when address is ambiguous — may reduce match accuracy

## How this service works

Retrieve chronological business-change events for an exact premises or, when explicitly requested, its parent building. The response discloses match scope and preserves suite identity.

## Output

An ordered list of business-change events for the queried premises, each event including a timestamp, event type, business identity, and suite information. The response also indicates the match scope used (exact_premise or building) and provides a pagination cursor for fetching subsequent pages.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "city": {
   "type": "string",
   "maxLength": 120,
   "minLength": 1
  },
  "limit": {
   "type": "integer",
   "default": 50,
   "maximum": 100,
   "minimum": 1
  },
  "cursor": {
   "type": "string",
   "maxLength": 512,
   "minLength": 1
  },
  "address": {
   "type": "string",
   "maxLength": 300,
   "minLength": 3
  },
  "locationId": {
   "type": "string",
   "format": "uuid",
   "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  },
  "matchScope": {
   "enum": [
    "exact_premise",
    "building"
   ],
   "type": "string",
   "default": "exact_premise"
  },
  "regionCode": {
   "type": "string",
   "maxLength": 16,
   "minLength": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/business-change-intelligence-api-location-timeline-d2da34eb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.businesschanges.dev](https://www.zero.xyz/host/api.businesschanges.dev/llms.txt)