> Trending Tokens
// Discover trending cryptocurrencies and tokens
Discover trending cryptocurrencies and tokens. Agents can request it by capability ID finance.trending, or by plain intent — EntRoute resolves phrases like “trending crypto”, “hot tokens” and “momentum tokens” to this capability.
EntRoute currently lists 2 endpoints from 2 providers for finance.trending, priced from $0.0001 to $0.01 per call, settled in USDC on Polygon and Base. The quickest responds in about 120ms at the 95th percentile. Every endpoint below is re-probed every 10 minutes for a valid 402 payment challenge; the ordering blends measured success rate, latency and price rather than provider claims.
These phrases resolve to this capability with intent-based discovery.
curl -X POST https://api.entroute.com/discover \ -H "Content-Type: application/json" \ -d '{"capability_id": "finance.trending"}'
Use this capability in your agent or application:
Frequently asked questions about Trending Tokens
How much does a trending tokens API call cost?
Endpoints listed for finance.trending on EntRoute are priced from $0.0001 to $0.01 per call. Payment is per request — there is no subscription, account or API key. Prices shown are read from each endpoint's live 402 response, not from a provider-supplied catalogue.
How do AI agents pay for trending tokens endpoints?
Via the x402 protocol. The agent calls the endpoint, receives an HTTP 402 Payment Required response describing the price and recipient, signs a stablecoin payment (USDC on Polygon and Base), and retries the request with proof of payment. The whole exchange takes seconds and needs no human approval.
How many providers offer trending tokens?
2 endpoints are currently listed for finance.trending across 2 providers. That number moves as endpoints are added and as failing ones are demoted.
Are these trending tokens endpoints verified?
Each one is probed every 10 minutes to confirm it still returns a well-formed 402 challenge on a payable network. Endpoints whose 7-day success rate drops below 50% are moved out of the ranked list into fallbacks with an explicit exclusion reason, so an agent can decide whether to retry them.