detect.halowerk.com
x402 API on Base, paid per request with x402.
- Endpoints10,725
- Price per requestfrom $0.001
- Outside payers · 7dn/a
- Answer 402169 of 184
Overview
- Seller wallet
- 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e
- Chains
- Base
- Hosts
- agent.halowerk.com, agentreadiness.halowerk.com, agri.halowerk.com, aialign.halowerk.com, atlantikland.halowerk.com, audio.halowerk.com, audit.halowerk.com, baltikum.halowerk.com, barriere.halowerk.com, bau.halowerk.com, bild.halowerk.com, bio.halowerk.com, bitcoin.halowerk.com, buero.halowerk.com, cms.halowerk.com, code.halowerk.com, commerce-baltic.halowerk.com, commerce-central.halowerk.com, commerce-change.halowerk.com, commerce-nord.halowerk.com, commerce-rules.halowerk.com, commerce-south.halowerk.com, commerce-southeast.halowerk.com, commerce-validator.halowerk.com, commerce-west.halowerk.com, conversion.halowerk.com, cosmos.halowerk.com, crawlspur.halowerk.com, creator.halowerk.com, dao.halowerk.com, daten.halowerk.com, datenvertrag.halowerk.com, defi.halowerk.com, denk.halowerk.com, dep.halowerk.com, detect.halowerk.com, dns.halowerk.com, doc.halowerk.com, energy.halowerk.com, ernte.halowerk.com, euroland.halowerk.com, fetch.halowerk.com, fetch.netzhandwerker.de, finanz.halowerk.com, finops.halowerk.com, forensik.halowerk.com, format.halowerk.com, formwerk.halowerk.com, fracht.halowerk.com, gaming.halowerk.com, geo.halowerk.com, gov.halowerk.com, grundpreis.halowerk.com, handel.halowerk.com, ident.halowerk.com, inhalt.halowerk.com, intel.halowerk.com, iot.halowerk.com, ip.halowerk.com, kalender.halowerk.com, karte.halowerk.com, kette.halowerk.com, klima.halowerk.com, lade.halowerk.com, landdossier.halowerk.com, landvergleich.halowerk.com, lauf.halowerk.com, mail.halowerk.com, markt.halowerk.com, material.halowerk.com, med.halowerk.com, medien.halowerk.com, mev.halowerk.com, mitteleuropa.halowerk.com, modell.halowerk.com, natur.halowerk.com, netz.halowerk.com, news.halowerk.com, news.netzhandwerker.de, nordland.halowerk.com, nostr.halowerk.com, ort.halowerk.com, ostland.halowerk.com, paket.halowerk.com, pfad.halowerk.com, postweg.halowerk.com, prop.halowerk.com, quantum.halowerk.com, rechen.halowerk.com, recht.halowerk.com, research.halowerk.com, rollup.halowerk.com, schild.halowerk.com, seo.halowerk.com, shot.halowerk.com, sicher.halowerk.com, sicht.halowerk.com, signal.halowerk.com, solana.halowerk.com, solar.halowerk.com, space.halowerk.com, sprach.halowerk.com, stable.halowerk.com, stack.halowerk.com, stack.netzhandwerker.de, staking.halowerk.com, standortdossier.halowerk.com, stat.halowerk.com, suedland.halowerk.com, tempo.halowerk.com, teuerung.halowerk.com, text.halowerk.com, ton.halowerk.com, tools.halowerk.com, vektor.halowerk.com, wallet.halowerk.com, webschutz.halowerk.com, webtechnik.halowerk.com, webwache.halowerk.com, welt.halowerk.com, wetter.halowerk.com, x402.halowerk.com, zoll.halowerk.com, zutritt.halowerk.com
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Other4,662Developer tools1,896Web data807Security693Commerce511Identity499Media451Onchain data445Market data312AI models286Search118Agents45
- First seen
- 2026-10-05 · last seen 2026-11-21
Endpoints
EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.https://paket.halowerk.com/v1/python-record-file-replacement-budget
Python package updates return the known bytes of added or changed files, with unresolved comparisons reported separately. Use it when an agent needs an incremental copy estimate between two recorded installations.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-record-largest-install-directory
Python package layout returns the leading top-level path component by recorded bytes and its known-byte share. Use it when an agent needs the largest directory contribution in a release manifest.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-record-metadata-payload-allocation
Python package footprint returns bytes in dist-info metadata and bytes in the remaining payload. Use it when an agent needs to separate metadata storage from application files.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-record-own-entry-convention
Python RECORD self-reference returns listed RECORD files and how many leave their own hash and size empty. Use it when an agent needs a manifest self-entry check at packaging time.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-record-portable-name-collisions
Python filename comparison returns collisions under NFC normalization, slash normalization and Unicode lowercase. Use it when an agent needs a portable-name comparison before moving an installation.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-record-repeated-content-bytes
Python package duplicates return groups of distinct paths with the same declared digest and size, and the repeated bytes. Use it when an agent needs potential savings if equal content can share storage.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-candidate-version-admission
Python dependency compatibility checks a candidate version against active constraints. Use it when an agent needs a version decision.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-direct-reference-inventory
Python package source metadata identifies dependency names installed from direct references and whether all are registry-based. Use it when an agent needs the source types required by a release.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-feature-extra-increment
Python package extras return the direct dependencies added by enabling one feature. Use it when an agent needs the incremental requirements of an installation extra.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-forwarded-feature-requests
Python feature propagation returns extras requested on dependencies by an active direct requirement. Use it when an agent needs downstream optional-feature requirements.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-interpreter-upgrade-diff
Python packaging compares active dependency names before and after a CPython minor-version change. Use it when an agent needs an interpreter migration check.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-operating-system-diff
Python package portability returns requirements added or removed when changing the target operating system. Use it when an agent needs a cross-platform installation comparison.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-pinning-profile
Python release constraints identify active exact pins and unconstrained direct package names. Use it when an agent needs the version-selection flexibility of a release.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-runtime-set
Python dependencies return the active package names for one target. Use it when an agent needs a release dependency inventory.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-simultaneous-clauses
Python dependency reconciliation identifies repeated normalized package names active within one target profile. Use it when an agent needs multiple constraints on one dependency.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/python-requirements-upper-bound-coverage
Python dependency bounds return the active names with no declared upper version restriction. Use it when an agent needs exposure to future dependency major releases.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-launch-year-lts-share
Software LTS release history reports the share of known long-term-support lines launched in a calendar year. Use it when an agent needs the LTS mix among releases.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-maintenance-only-cohort
Software maintenance status counts active and post-active release lines with documented phase dates on a given day. Use it when an agent needs a patch-maintenance workload forecast.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-maintenance-phase-lengths
Software maintenance phases return the length of active and post-active standard support for a release. Use it when an agent needs phase lengths before retirement.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-migration-overlap
Software migration window returns overlapping standard support days for two release lines. Use it when an agent needs a migration interval before support expires.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-parallel-support-peak
Software support concurrency finds the first day on which the most documented release lines overlap in a period. Use it when an agent needs the largest simultaneous support workload.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-release-interval-median
Software release cadence returns the median number of days between consecutive distinct release-line start dates inside a period. Use it when an agent needs an observed release cadence.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-retirement-quarter
Software retirement calendar lists all release lines of a product with a published end date in one quarter. Use it when an agent needs a quarterly retirement workload.
BaseCommerce$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-stack-support-horizon
Software stack support returns the common support interval for release lines from two different products. Use it when an agent needs a shared support horizon for a deployed stack.
BaseCommerce$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-successor-runway
Software release migration identifies the successor available at retirement with the longest remaining support. Use it when an agent needs an upgrade target at a documented cutoff.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/runtime-calendar-uncovered-days
Software support coverage totals calendar days outside every documented standard-support interval and reports the first gap. Use it when an agent needs continuity of documented coverage.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-bundled-parser-list-recognition-gap
SPDX package compatibility returns identifiers recognized by the live list and the locally installed npm license-ID snapshot. Use it when an agent needs to explain a registry versus build-tool vocabulary mismatch.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-declared-license-id-inventory
Package license identifiers return current, deprecated and unrecognized declarations against the published SPDX list. Use it when an agent needs to audit a package metadata inventory.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-exception-register-evidence
License exception lookup returns the official exception title, deprecation flag and reference domains for a WITH identifier. Use it when an agent needs to verify an exception identifier in package data.
BaseIdentity$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-package-release-declaration-delta
Package license changes return added and removed SPDX declarations and OSI listing flags for newly added IDs. Use it when an agent needs to review license metadata changes between package releases.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-published-license-title-search
Software license search returns official SPDX identifiers matching all supplied title words. Use it when an agent needs the identifier behind a human-readable license name.
BaseCommerce$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-reference-text-digest-equality
License evidence returns whether a supplied SHA-256 matches the exact UTF-8 licenseText field published by SPDX. Use it when an agent needs to verify a license text fingerprint without transmitting the text.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-source-reference-verification-record
Software license references return SPDX-recorded live and archived link counts, source domains and the latest check time. Use it when an agent needs the provenance of a license listing.
BaseCommerce$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-standard-file-header-footprint
Software license headers return whether SPDX provides a standard per-file notice, its line count and its UTF-8 checksum. Use it when an agent needs to identify the official short notice in release tooling.
BaseDeveloper tools$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-template-variable-and-optional-inventory
License matching templates return variable names and counts of optional sections in the official SPDX template. Use it when an agent needs to determine which fields a text matcher must handle.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/spdx-version-qualified-identifier-options
SPDX version identifiers return the published only and or-later forms for a license version stem. Use it when an agent needs to inspect ambiguous historical version spelling without automatically selecting terms.
BaseOther$0.005/ request
2026-11-19
https://paket.halowerk.com/v1/wheel-linux-artifact-policy-diff
Python wheel platform comparison lists normalized libc policies introduced and removed between two supplied WHEEL declarations. Use it when an agent needs a platform policy diff across release artifacts.
BaseDeveloper tools$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-fleet-decision
Python wheel fleet coverage evaluates each supplied runtime and lists the indices excluded by the wheel’s platform policies. Use it when an agent needs coverage of a mixed deployment fleet.
BaseOther$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-host-policy-match
Python wheel Linux compatibility identifies which declared platform tags match an explicit libc family, version and machine architecture. Use it when an agent needs a platform-only compatibility verdict.
BaseOther$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-host-upgrade-floor
Python wheel runtime upgrade identifies the closest declared compatible libc floor above the supplied host version. Use it when an agent needs the minimum version change relevant to one host.
BaseOther$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-installer-policy-generation
Python wheel installer generation identifies whether an artifact has legacy manylinux spellings, modern policies only, or neither. Use it when an agent needs the spelling support a platform-tag parser needs.
BaseDeveloper tools$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-legacy-equivalence
Python wheel legacy normalization replaces historical manylinux names with their PEP 600 glibc policy equivalents. Use it when an agent needs the relationship between old and current platform labels.
BaseDeveloper tools$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-libc-family-split
Python wheel platform split separates architectures declared for both libc families from those listed for just one. Use it when an agent needs the glibc and musl coverage gap.
BaseOther$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-native-only-tags
Python wheel portability audit distinguishes unversioned native Linux architecture tags from portable policy declarations. Use it when an agent needs unversioned tags needing host-specific review.
BaseSecurity$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-portable-baselines
Python wheel platform baselines report the earliest declared libc version for each architecture and libc family. Use it when an agent needs the minimum advertised runtime floors.
BaseOther$0.005/ request
2026-11-20
https://paket.halowerk.com/v1/wheel-linux-redundant-floors
Python wheel platform redundancy identifies stricter tags whose entire supported runtime range an existing lower floor covers. Use it when an agent needs redundant manylinux or musllinux declarations.
BaseOther$0.005/ request
2026-11-20
https://prop.halowerk.com/v1/building-degree-hour-energy
Integrate supplied heating degree-hours into useful and input energy under a declared conductance.
BaseOther$0.005/ request
2026-11-18
https://prop.halowerk.com/v1/building-finish-pack-rounding
Compare pooled versus per-room finish-pack purchases under supplied area and waste assumptions.
BaseOther$0.005/ request
2026-11-18
https://prop.halowerk.com/v1/building-lease-common-area-allocation
Allocate declared common area by supplied unit weights and reconcile net and inclusive areas.
BaseOther$0.005/ request
2026-11-18
https://prop.halowerk.com/v1/building-ventilation-co2-balance
Return a well-mixed steady CO2 balance and required airflow under declared generation and target values.
BaseOnchain data$0.005/ request
2026-11-18
Evidence
Answers HTTP 402
Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.169 of 184
169 of 184 probed endpoints answered HTTP 402 with a parseable payment payload
checked 2026-11-21
x402-style payments, 7-day window (Base)
x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.unknown
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read))
window ended 2026-11-19
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e | 10,725 | 169 of 184 probed endpoints answered HTTP 402 with a parseable payment payload 2026-11-21 | unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read)) |
One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.
Pricing
The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.
Claim this merchant
Sign a message from the payout address 0x2880ed…1c4e5e to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.
Data CC-BY-4.0, attribution: data by satohub.ai. Data: x402-list.com (CC BY 4.0). Data as of 2026-11-21. Appearing here is not an endorsement. Check an endpoint with the doctor.