MARKET MONITOR / CATALOGUE Services 167,156 MCP listed 53,480 x402 113,832 Rails Base / Solana / Polygon / Arbitrum Imported 2026-11-20 · 3 sources
Provider

format.halowerk.com

format.halowerk.com · 162 listed services · provider site

Services by format.halowerk.com

Civil clock hour bin exposure x402 REST usage

Timezone hourly reporting returns actual minutes represented by each of the 24 hour labels on a local date. Use it when an agent needs correct denominators for hourly activity.

format.halowerk.com Web & Scraping 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock skipped date register x402 REST usage

Civil calendar history identifies entire dates removed by a dateline change during a UTC year. Use it when an agent needs a historical date omitted by a local calendar.

format.halowerk.com Comms & Messaging 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock pay band real minutes x402 REST usage

Payroll time bands count real, skipped and doubled minutes inside a half-open local wall-clock interval. Use it when an agent needs time-band occupancy over a clock change.

format.halowerk.com Other services 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Json pointer resolution trace x402 REST usage

JSON Pointer resolution: return the selected JSON value or the first segment that cannot be resolved. Use it when an agent needs to resolve an RFC 6901 reference in a document.

format.halowerk.com Productivity & Docs 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock utc log wall order x402 REST usage

Timezone event ordering detects equal or backward wall-clock labels in a strictly increasing UTC event sequence. Use it when an agent needs an explanation of apparent clock reversals.

format.halowerk.com Infrastructure 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock shift duration alternatives x402 REST usage

Work shift duration returns all chronologically possible elapsed minutes between two local labels. Use it when an agent needs the duration bounds of a shift with ambiguous endpoints.

format.halowerk.com Infrastructure 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Json numeric interoperability report x402 REST usage

JSON numeric interoperability: count unsafe integers and values that overflow binary64. Use it when an agent needs to protect identifiers and exact numeric values across runtimes.

format.halowerk.com Productivity & Docs 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock observed offset witness x402 REST usage

Timezone verification checks a recorded UTC offset against the real candidate instants of a local timestamp. Use it when an agent needs to verify an offset supplied by a device.

format.halowerk.com Other services 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock recurring local appointment count x402 REST usage

Local appointment scheduling counts skipped, unique and repeated occurrences of one wall time over a date span. Use it when an agent needs a recurrence count across clock changes.

format.halowerk.com Other services 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Ndjson record key uniqueness x402 REST usage

NDJSON record key uniqueness: report repeated scalar values at a JSON Pointer across records. Use it when an agent needs to verify that a streaming file has unique record identifiers.

format.halowerk.com Productivity & Docs 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Civil clock year shift budget x402 REST usage

Timezone changes return the UTC transition instants and total forward and backward clock minutes in one UTC year. Use it when an agent needs an annual offset-change inventory.

format.halowerk.com Other services 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Column rowgroup predicate pruning x402 REST usage

Return row-group pruning decisions.

format.halowerk.com Other services 1 calls / 30d checked 2026-11-19
0.005 USDC per call per call

Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.