# FanPulse Timeline API

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

Returns canonical in-universe chronology for major franchises, including eras, pivotal events, recommended watch/read order, and lore gaps.

## Facts

- Endpoint: GET https://fanpulse-tau.vercel.app/api/fan/timeline
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fanpulse-timeline-api-30171ca1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__6WhaS1AWo8XqCbBItV5x

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 fanpulse-timeline-api-30171ca1
```

Example prompt: Can you give me the full in-universe chronological timeline for the Star Wars franchise — all the eras, pivotal events, the correct watch order, and any known lore gaps?

## When to prefer this

Use this endpoint when an agent needs structured, canonical, in-universe chronological data for a major entertainment franchise — particularly when the user wants era breakdowns, event ordering, watch/read sequencing, or wants to understand lore gaps. Prefer over general web search when structured, curated franchise chronology is needed rather than raw search results.

## Known failure modes

- Franchise not supported — returns empty or error if the queried franchise is outside the supported list (Star Wars, Harry Potter, LOTR, Star Trek, Marvel, Game of Thrones)
- Payment not processed — x402 payment of 0.1 USDC required per call; missing payment returns 402 error
- Ambiguous franchise query — overly vague inputs may return generic or mismatched timelines
- Rate limiting — repeated rapid calls may be throttled

## How this service works

Canonical in-universe chronology for fan and entertainment agents. Returns eras, pivotal events, watch/read order, and lore gaps for major franchises.

## Output

Returns structured chronological data for the requested franchise including named eras, key pivotal events in order, recommended watch or read order, and identified lore gaps or unresolved canon questions.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fanpulse-timeline-api-30171ca1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fanpulse-tau.vercel.app](https://www.zero.xyz/host/fanpulse-tau.vercel.app/llms.txt)