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:68eca8dd7938a7458fbd26b6

What it does

Web3 Trader is an x402-protocol endpoint hosted on Questflow's infrastructure that provides real-time cryptocurrency data aggregation and analysis. It accepts a natural-language prompt via a POST request with an `input` field and returns a text response from the agent. 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 capabilities 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 decimals). The endpoint accepts POST requests 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 tool calls before responding.

Note that this is a development/testnet endpoint (api-dev subdomain, Base Sepolia network). 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. The agent's actual reliability, data freshness, and response quality could not be verified from available materials.

Capabilities

crypto-token-lookupmarket-data-aggregationprice-trackingdefi-pool-analysistrending-coinstrending-nftstop-gainers-loserstwitter-posttwitter-replytwitter-retweettwitter-mention-monitoringtwitter-searchx402-paymentbase-sepolia-usdc

Use cases

  • —Look up token information and market metrics by contract address
  • —Monitor top gaining and losing cryptocurrencies in real time
  • —Analyze DeFi liquidity pools across multiple networks
  • —Fetch trending coins, NFTs, and categories for market research
  • —Automate Twitter engagement: post, reply, retweet, and search tweets

Fit

Best for

  • —Agents needing on-demand crypto market data without API key management
  • —Automated social media workflows tied to crypto market events
  • —Quick lookups of DeFi pool data across chains

Not for

  • —Production trading systems (this is a dev/testnet endpoint on Base Sepolia)
  • —Users needing guaranteed SLAs or documented rate limits
  • —High-frequency trading requiring sub-second latency

Quick start

curl -X POST https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68eca8dd7938a7458fbd26b6 \
  -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": "Here are the top 5 trending coins: 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:68eca8dd7938a7458fbd26b6
Transporthttp
Protocolx402
Pay to0x7668F349CfE601c48e5b5b4bFf9d287fA137d987
CurrencyUSDC

Quality

0.30/ 1.00

No OpenAPI spec, no documentation pages, no example responses, and the endpoint is on a dev/testnet network (Base Sepolia). The only structured information comes from the x402 challenge metadata. The response schema and actual capabilities are inferred from the description string and cannot be independently verified.

Warnings

  • —Development/testnet endpoint (Base Sepolia) — not suitable for production use
  • —No OpenAPI specification or documentation found (all /docs, /api, /pricing, /README return 404)
  • —Response example is fabricated for illustration; actual agent output format is unverified
  • —maxAmountRequired of 500000 units — likely 0.50 USDC but denomination not explicitly confirmed
  • —1200-second max timeout suggests potentially slow or multi-step agent responses
  • —Twitter management capabilities may require additional authentication not described in the schema

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/f7wXRb