# FanPulse Franchise Timeline

> FanPulse Franchise Timeline is a paid API for AI agents from fanpulse.theaslangroupllc.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

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

## Facts

- Endpoint: GET https://fanpulse.theaslangroupllc.com/api/fan/timeline
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fanpulse-franchise-timeline-f41f1dc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UJyxu4iY7d_eeO25yXxTI

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-franchise-timeline-f41f1dc0
```

Example prompt: Can you pull up the full in-universe chronology for Star Wars — including all the major eras, pivotal events, the correct watch order across films and shows, and any known lore gaps?

## When to prefer this

Use this endpoint when a user needs structured chronological or era-based navigation of a major entertainment franchise — especially when watch/read order, canonical event sequencing, or lore gap identification is the goal. Prefer over general web search when authoritative in-universe ordering matters.

## Known failure modes

- Franchise not supported — returns empty or error if the requested franchise is not in the database
- Ambiguous franchise name — may return results for wrong universe if name is shared
- Lore gaps field may be sparse for smaller or well-documented franchises
- API returns 402 if payment of 0.1 USDC is not attached to the request

## 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

A structured response containing the canonical in-universe chronology for the requested franchise: named eras with descriptions, pivotal events in sequence, recommended watch or read order, and identified lore gaps or continuity inconsistencies.

## 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-franchise-timeline-f41f1dc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fanpulse.theaslangroupllc.com](https://www.zero.xyz/host/fanpulse.theaslangroupllc.com/llms.txt)