PA
Utilities · x402 · early usage

Returns the full version history of a package from a single normalised schema that cove…

Returns the full version history of a package from a single normalised schema that covers seven ecosystems. Versions are ordered by semantic version, not alphabetically and not in registry order, so 1.10.0 sorts after 1.9.0 — the mistake that quietly breaks n…

by paket.halowerk.com · discovered, not yet claimed by its owner · updated 2026-10-08

30d calls3
30d payers3
MethodPOST
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Returns the full version history of a package from a single normalised schema that covers seven ecosystems. Versions are ordered by semantic version, not alphabetically and not in registry order, so 1.10.0 sorts after 1.9.0 — the mistake that quietly breaks naive comparisons. For each version you get the publication timestamp, whether it is the registry default, whether it is deprecated and the deprecation reason as the registry states it.

Tags: bazaar

Call contract

Method
POST
Input
json
Output
json
Last paid call
2026-10-08
Input example from Bazaar metadata
{
  "include_prereleases": true,
  "limit": 200,
  "name": "express",
  "system": "npm"
}
No output exampleProvider did not publish one in Bazaar metadata.

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/55181.json for the price and payment options.
  3. Pay. Call GET https://paket.halowerk.com/v1/package-versions. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.003 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
3 calls · 3 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.0030x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "3000",
    "amountUsd": 0.003,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl
curl "https://paket.halowerk.com/v1/package-versions"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://paket.halowerk.com/v1/package-versions");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://paket.halowerk.com/v1/package-versions")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
paket.halowerk.com
Endpoint
https://paket.halowerk.com/v1/package-versions
Machine-readable
/resources/55181.json