What changed in the listing

crypto-news returns recent cryptocurrency headline metadata and per-headline sentiment. Its September 20 update changes the opening of its description in bankr.x402.json from “Crypto news API” to “Crypto news aggregator API.”

One added word. For an agent choosing a tool from its description, that word names a specific job: collecting relevant crypto headlines for a research request or recurring news brief.

The September 20 registry diff changes only that wording. The rest of the description stays intact. Callers still get article URLs and publisher domains, with timestamps and other metadata attached to the results.

The change gives routers an explicit match for requests such as “find a crypto news aggregator.” It doesn't establish that search coverage has expanded or that results arrive faster. Those would require separate evidence.

The price and request contract stay put

The registry still sets price to "0.005", with currency: "USDC" and network: "base". That's $0.005 USDC per call through x402 on Base mainnet. The paymentScheme remains "exact", and the supported method is POST.

At that listed rate, 100 calls cost $0.50 in endpoint charges.

The input fields also remain unchanged:

| Field | Accepted input | |---|---| | topic | crypto, markets, defi, bitcoin, ethereum, or stablecoins; default crypto | | query | Optional search override, up to 240 characters | | limit | Requested headline count from 1 to 30; default 10 | | hours | Lookback from 1 to 168 hours; default 48 |

These values come from the crypto-news registry entry. Existing callers don't need a request migration for this update.

Want the most recent day's stablecoin headlines? This JSON body selects that preset and narrows the default lookback: 

{
  "topic": "stablecoins",
  "hours": 24,
  "limit": 10
}

For a specific event, use query as the search override: 

{
  "query": "Ethereum staking withdrawals",
  "hours": 12,
  "limit": 8
}

These are request bodies for crypto-news, ready to pass through your x402-capable caller. They aren't sample results.

Refresh the description your router reads

If your agent stores endpoint descriptions locally, refresh its crypto-news entry. A router working from an older copy won't see the added aggregator wording.

And if you maintain an index for tool selection, rebuild the affected entry after updating the text. Keep the endpoint identifier crypto-news; the release doesn't introduce a replacement name.

A useful routing check is to ask your agent for “a crypto news aggregator covering stablecoins over the last 24 hours.” Inspect whether it selects crypto-news and supplies topic: "stablecoins" with hours: 24.

That checks your integration. It doesn't prove a general improvement in routing accuracy.

For existing integrations, keep the current response parser unless a separate contract change calls for an edit. A description revision alone isn't a reason to change how your application reads results.

Use the web-probe result as research input

Within web-probe, this endpoint fits tasks that start with recent crypto coverage. A briefing agent can collect headlines before choosing which linked articles deserve further reading.

The description promises headline metadata, including country and language information. Plan any full-article reading as a separate step, and retain each article's URL beside claims your agent extracts from it.

But set the time window deliberately. A daily brief can request hours: 24; a week-long review can use hours: 168. The default is 48 hours, so repeated daily requests can cover overlapping periods.

If you're keeping a running digest, check returned URLs against stories you've already recorded before adding them again. Treat per-headline sentiment as a label on the coverage. Keep it attached to the relevant article when passing results to the next agent.