# ChronicaPulse Timeline

> ChronicaPulse Timeline is a paid API for AI agents from chronicapulse.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Generates a chronological narrative timeline for a person, place, or topic sourced from historical newspaper archives

## Facts

- Endpoint: GET https://chronicapulse.vercel.app/api/chronica/timeline
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chronicapulse-timeline-10095b47
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M0DE9Wd6mYfJj7-KatpO0

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-timeline-10095b47
```

Example prompt: Can you pull together a chronological timeline narrative for my great-grandfather Heinrich Brauer — I want to see how he appeared in historical newspapers from the 1890s through the 1940s, covering his life story as found in digitized archive records?

## When to prefer this

Use this endpoint when you need a synthesized, narrative chronological view of a person, place, or topic across time — particularly for genealogy, family history, or historical research. Prefer this over the raw archive search endpoint when you want a coherent story rather than individual search results, and over the person or place-specific endpoints when your subject spans multiple domains (births, events, places) and you need a unified timeline.

## Known failure modes

- No records found for the specified subject in the archive — returns empty or minimal results
- Subject name too ambiguous — returns records for multiple unrelated individuals
- Date range too narrow — insufficient coverage for meaningful timeline
- Archive gaps for certain time periods or geographic regions — narrative may be incomplete
- Invalid or missing required parameters — returns 400 error
- Payment not processed — returns 402 Payment Required

## How this service works

Chronological timeline for genealogy and research agents. Returns a narrative for a person, place, or topic across historical newspaper archives.

## Output

A chronological narrative timeline covering newspaper mentions of the queried person, place, or topic across historical newspaper archives, including dates, event summaries, and source citations arranged in time order.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "subject"
 ],
 "properties": {
  "lang": {
   "type": "string",
   "description": "lang"
  },
  "type": {
   "type": "string",
   "description": "type"
  },
  "subject": {
   "type": "string",
   "description": "subject"
  },
  "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-timeline-10095b47/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chronicapulse.vercel.app](https://www.zero.xyz/host/chronicapulse.vercel.app/llms.txt)