x402-payable AI agent (AIXBT) on Questflow — send a message, pay in USDC on Base, get a response.
What it does
AIXBT Agent is an x402-enabled AI agent hosted on Questflow's platform, accessible via a single POST endpoint. Callers send a text message in the request body and receive a text response from the agent. Payment is handled inline via the x402 protocol: the endpoint requires an X-PAYMENT header carrying a USDC payment on the Base network (up to 100,000 units, i.e. 0.10 USDC given 6-decimal precision). The maximum request timeout is 1,200 seconds.
Questflow positions itself as a platform for autonomous AI "Clones" that scan and trade across on-chain markets (Polymarket, Pump.fun, OKX, Opinion Labs, etc.). The AIXBT Agent appears to be one such agent exposed for programmatic interaction. However, the crawled material provides no specific documentation about what domain expertise AIXBT offers, what data sources it draws on, or what kinds of queries it handles best. The endpoint's own description calls it "a sophisticated AI agent designed to provide intelligent assistance and automated solutions," but no concrete capabilities, rate limits, SLAs, or example conversations are documented.
Because there is no OpenAPI spec, no dedicated docs page, and no usage examples beyond the x402 challenge metadata, consumers should treat this as a lightly-documented, experimental endpoint. The output schema is simple: a single string response field. There is no streaming, no tool-use protocol, and no structured output beyond plain text.
Capabilities
Use cases
- —Sending ad-hoc questions to an AI agent and paying per request in USDC on Base
- —Integrating a pay-per-call AI assistant into an autonomous agent pipeline via x402
- —Querying an on-chain-aware AI agent from a wallet-enabled application
Fit
Best for
- —Developers experimenting with x402 micropayment-gated AI endpoints
- —Agent-to-agent workflows that need a simple text-in/text-out AI call with crypto payment
- —Users who want to interact with Questflow agents programmatically rather than through the web UI
Not for
- —Production workloads requiring documented SLAs, rate limits, or guaranteed uptime
- —Use cases needing structured or multi-turn conversational state
- —Users who need free or fiat-billed AI chat endpoints
Quick start
curl -X POST https://api.questflow.ai/x402/agent/qrn:agent:68a68dea6913f9f1c46e2666 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{"input": "What is the current sentiment on ETH?"}'Example
Request
{
"input": "What is the current sentiment on ETH?"
}Response
{
"response": "Current sentiment on ETH is cautiously bullish, driven by strong ETF inflows and on-chain accumulation by large holders."
}Endpoint
Quality
The x402 challenge provides a minimal input/output schema and payment details, but there is no OpenAPI spec, no dedicated documentation, no usage examples, and no information about the agent's actual domain expertise or limitations. Most listing fields are inferred from very sparse metadata.
Warnings
- —No OpenAPI or dedicated API documentation found — /docs, /api, /pricing, /README all return 404.
- —Agent capabilities and domain expertise are unspecified; the description is generic boilerplate.
- —Exact USDC cost is ambiguous: 100,000 units could mean $0.10 (6-decimal USDC) but this is not explicitly confirmed.
- —No rate limits, SLAs, or uptime guarantees documented.
- —The response example is fabricated for illustration; actual agent output is unknown.
Citations
- —x402 challenge requires USDC payment on Base network with maxAmountRequired of 100000 and payTo address 0x1D03…6f9Dhttps://api.questflow.ai/x402/agent/qrn:agent:68a68dea6913f9f1c46e2666
- —Asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC on Base)https://api.questflow.ai/x402/agent/qrn:agent:68a68dea6913f9f1c46e2666
- —maxTimeoutSeconds is 1200https://api.questflow.ai/x402/agent/qrn:agent:68a68dea6913f9f1c46e2666
- —Questflow aggregates Polymarket, Pump.fun, Opinion Labs, OKX and other on-chain marketshttps://api.questflow.ai