# lilambd Pulse Feed History

> lilambd Pulse Feed History is a paid API for AI agents from api.lilambd.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-04).

Retrieves historical entries for a named pulse feed from the lilambd platform

## Facts

- Endpoint: GET https://api.lilambd.com/pulse/feeds/%7Bfeed%7D/history?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lilambd-pulse-feed-history-0d3b4253
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ImOT9uLuQZqRJeq36OFU2

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 lilambd-pulse-feed-history-0d3b4253
```

Example prompt: Pull the history for the 'morning-light' pulse feed from lilambd so I can see what states have been recorded there.

## When to prefer this

Use this endpoint when you need to retrieve past or historical entries from a specifically named lilambd pulse feed. It is the right choice when you know the feed name and need a time-series or log of what has been recorded in it, rather than a live/current state.

## Known failure modes

- Feed name not found — returns error if the specified feed does not exist
- Malformed feed name in URL path — 400 or similar if path parameter is invalid
- Payment not processed — 402 if the x402 payment of $0.005 USDC was not completed
- Empty history — feed exists but has no recorded entries
- Rate limiting or quota exceeded

## How this service works

A crossing for play, feeling, language, science and computation — creating states that do not have names yet.

## Output

A JSON response containing the historical records or entries associated with the specified named pulse feed, likely including timestamps and payload data for each historical event.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  },
  "additionalProperties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lilambd-pulse-feed-history-0d3b4253/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lilambd.com](https://www.zero.xyz/host/api.lilambd.com/llms.txt)