# ChronicaPulse Place History API

> ChronicaPulse Place History API is a paid API for AI agents from chronicapulse.theaslangroupllc.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-16).

Returns the newspaper history of any town, city, or neighborhood for genealogy and research purposes

## Facts

- Endpoint: GET https://chronicapulse.theaslangroupllc.com/api/chronica/place
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chronicapulse-place-history-api-4f425423
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tcwHjt9hTk2ggFASknjMM

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 chronicapulse-place-history-api-4f425423
```

Example prompt: Can you pull up the newspaper history for Galveston, Texas? I'm researching my family's roots there and want to see what historical coverage exists about the town.

## When to prefer this

Use this endpoint when you need historical newspaper coverage specifically tied to a geographic place — a town, city, or neighborhood — rather than a person, business, or event. Ideal for genealogy agents building place-level context, local historians, or researchers trying to understand the historical character and recorded past of a location.

## Known failure modes

- Place name not recognized or too ambiguous — may return empty results or an error
- No newspaper coverage found for a very small or obscure locality
- Misspelled or historically renamed place names may yield no results
- Rate limiting or payment failure via x402 protocol returns 402 status
- Overly broad place names (e.g. 'downtown') without a city/state may fail to resolve

## How this service works

Place history research for genealogy and research agents. Returns the newspaper history of any town, city, or neighborhood.

## Output

A narrative or structured summary of the newspaper history of the specified town, city, or neighborhood, drawn from digitized historical newspaper archives — including notable local events, coverage periods, and relevant historical context for that place.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "place"
 ],
 "properties": {
  "lang": {
   "type": "string",
   "description": "lang"
  },
  "place": {
   "type": "string",
   "description": "place"
  },
  "year_end": {
   "type": "string",
   "description": "year_end"
  },
  "year_start": {
   "type": "string",
   "description": "year_start"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chronicapulse-place-history-api-4f425423/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chronicapulse.theaslangroupllc.com](https://www.zero.xyz/host/chronicapulse.theaslangroupllc.com/llms.txt)