# Time Labels Prior Text-Set Comparison

> Time Labels Prior Text-Set Comparison is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-16).

Extracts text content from HTML <time> elements matching a given attribute filter and compares it against a supplied set of previous text values to identify changes.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-web-times-compare?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/time-labels-prior-text-set-comparison-0db8ffc4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xtSwGA91rd7Gutg5muSrl

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 time-labels-prior-text-set-comparison-0db8ffc4 -d '<json body>'
```

Example prompt: Check the <time> element with id='publish-date' on https://example.com/article and tell me if its text has changed from any of these previous values: 'January 5, 2024', 'February 10, 2024'.

## When to prefer this

Use this endpoint when you need to detect whether a specific <time> HTML element on a public webpage has changed its text content compared to a known set of historical values. It is ideal for lightweight change monitoring of static HTML pages without needing a full browser or JavaScript rendering. Prefer this over general-purpose scrapers when the target is specifically a <time> element and structured prior-comparison output is needed rather than raw HTML extraction.

## Known failure modes

- URL is inaccessible or returns non-200 HTTP status
- HTML contains no <time> elements matching the specified attribute and value
- JavaScript-rendered content not visible (static parsing only)
- Login-gated or paywalled pages return incomplete HTML
- previous_texts array is empty, making comparison trivial
- attribute pattern does not match schema regex, causing validation error
- HTML payload exceeds 100,000 character limit

## How this service works

Time labels — Prior text-set comparison: Prior text-set comparison for Time labels. One public HTTPS page or supplied HTML; static parsing, no JavaScript rendering, login or access bypass. Specialised preset in a shared 50-profile, 20-operation engine. 0.01 USDC includes one bounded prior text-set comparison result.

## Output

Returns a bounded comparison result indicating whether the current text content of the matched <time> HTML element differs from any of the supplied previous text values, along with the current extracted text.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "default": "",
   "maxLength": 2048
  },
  "html": {
   "type": "string",
   "default": "<!doctype html><html><head></head><body><time id=\"sample\" data-kind=\"example\">Example product guide</time></body></html>",
   "maxLength": 100000
  },
  "term": {
   "type": "string",
   "default": "product",
   "maxLength": 100,
   "minLength": 1
  },
  "attribute": {
   "type": "string",
   "default": "id",
   "pattern": "^[a-zA-Z][a-zA-Z0-9:_-]{0,49}$",
   "maxLength": 50
  },
  "previous_texts": {
   "type": "array",
   "items": {
    "type": "string",
    "default": "",
    "maxLength": 1000
   },
   "default": [
    "Older example"
   ],
   "maxItems": 200,
   "minItems": 0
  },
  "attribute_value": {
   "type": "string",
   "default": "sample",
   "maxLength": 200
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/time-labels-prior-text-set-comparison-0db8ffc4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)