Groups managed news feeds into events when an agent needs a compact news briefing
Groups managed news feeds into events when an agent needs a compact news briefing. Supply topic, language, time window and result limit using the published schema. Returns headlines, a short abstract, first-report time, reporting-source counts and citations.…
by news.halowerk.com · discovered, not yet claimed by its owner · updated 2026-10-11
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
Groups managed news feeds into events when an agent needs a compact news briefing. Supply topic, language, time window and result limit using the published schema. Returns headlines, a short abstract, first-report time, reporting-source counts and citations. Coverage is limited to the managed feed set; source count is not independent confirmation. Third-party article bodies are never returned.
Tags: x402 · halowerk · news_events · bazaar
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/52486.jsonfor the price and payment options. - Pay. Call
GET https://news.halowerk.com/news. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with 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.002 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Calls (30d)
- 2 · 2 unique payers (third-party data from the public x402 Bazaar)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.002 | 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "2000",
"amountUsd": 0.002,
"maxTimeoutSeconds": 300
}
]Examples
curl "https://news.halowerk.com/news"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://news.halowerk.com/news");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://news.halowerk.com/news")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- news.halowerk.com
- Endpoint
- https://news.halowerk.com/news
- Machine-readable
/resources/52486.json