x402base-sepoliaquality 0.30

x402-payable agent for real-time crypto data, DeFi pool analysis, trending tokens, and Twitter management.

Price
0.5 USDC / call
Protocol
x402
Verified
no
Endpoint
https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68ecc0ccd2f1fd7645d7e820

What it does

Web3 Trader is an x402-enabled AI agent endpoint hosted on Questflow's infrastructure that provides real-time cryptocurrency data aggregation and analysis. It accepts a natural-language text input via POST and returns agent-generated responses. Capabilities described in the x402 challenge metadata include token information lookup by contract address, comprehensive market data retrieval, price tracking with market metrics, identification of top gaining and losing coins, DeFi pool analysis across multiple networks, and fetching trending coins, NFTs, and categories. It also includes Twitter/X management features such as posting, replying, retweeting, monitoring mentions, and searching tweet content.

Payment is handled via the x402 protocol on Base Sepolia using USDC (contract 0x036CbD53842c5426634e7929541eC2318f3dCF7e) with a maximum amount of 500,000 units (likely 0.50 USDC given 6-decimal USDC). The endpoint accepts an HTTP POST with a JSON body containing a single "input" string field and returns a JSON object with a "response" string field. The maximum timeout is 1200 seconds, suggesting the agent may perform multi-step reasoning or external API calls before responding.

Note that this endpoint is on a development domain (api-dev) and uses Base Sepolia (a testnet), indicating it is not yet in production. No OpenAPI spec, dedicated documentation, or pricing page was found. The underlying platform is Questflow, which markets itself as an AI agent economy for onchain market scanning and trading.

Capabilities

crypto-market-datatoken-lookupdefi-pool-analysistrending-coinsnft-trendingprice-trackingtop-gainers-loserstwitter-postingtwitter-mentionstwitter-searchx402-paymentnatural-language-inputbase-sepolia-usdc

Use cases

  • —Query real-time token prices and market metrics by contract address
  • —Identify top gaining and losing cryptocurrencies
  • —Analyze DeFi liquidity pools across multiple networks
  • —Fetch trending coins, NFTs, and categories
  • —Post tweets, reply, retweet, and monitor Twitter mentions programmatically

Fit

Best for

  • —AI agents needing on-demand crypto market intelligence via natural language
  • —Developers prototyping x402-paid crypto data workflows on testnet
  • —Automated social media management tied to crypto market events

Not for

  • —Production trading systems requiring mainnet settlement and SLAs
  • —Users needing structured, schema-defined REST endpoints with predictable field-level output
  • —High-frequency trading where 1200-second timeout is unacceptable

Quick start

curl -X POST https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68ecc0ccd2f1fd7645d7e820 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-header>" \
  -d '{"input": "What are the top 5 trending coins right now?"}'

Example

Request

{
  "input": "What are the top 5 trending coins right now?"
}

Response

{
  "response": "The top 5 trending coins right now are: 1. Bitcoin (BTC) ... 2. Ethereum (ETH) ... 3. Solana (SOL) ... 4. Pepe (PEPE) ... 5. Dogecoin (DOGE) ..."
}

Endpoint

URLhttps://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68ecc0ccd2f1fd7645d7e820
Transporthttp
Protocolx402
Pay to0x919aAa8A70da79f6184E6D0094E7F4BfB8aa65db
CurrencyUSDC

Quality

0.30/ 1.00

No OpenAPI spec, no documentation pages, no examples of actual responses, and the endpoint runs on a testnet (Base Sepolia dev environment). The only structured metadata comes from the x402 challenge. The response example above is entirely inferred. Effectively a stub listing.

Warnings

  • —Endpoint is on a development domain (api-dev) and uses Base Sepolia testnet — not production-ready
  • —No OpenAPI specification or documentation found; /docs, /api, /pricing, /README all return 404
  • —Output schema is a single free-text string; no structured/typed response fields
  • —maxTimeoutSeconds is 1200 (20 minutes), suggesting potentially very long response times
  • —Response example is inferred — no actual sample response was available
  • —Twitter management capabilities are self-described and unverified

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 18:32:16Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/yjrXZC