x402-payable AI agent endpoint on Questflow's swarm platform, accepting USDC on Base Sepolia.
What it does
This endpoint exposes an AI agent ("new creation") on Questflow's swarm infrastructure via the x402 payment protocol. Callers send a POST request with a JSON body containing an `input` string (a message to the agent) and receive a `response` string back. Payment is handled through the x402 challenge-response flow using USDC on the Base Sepolia testnet, with a maximum amount of 500,000 units (likely 0.50 USDC given 6-decimal USDC) per request and a timeout of up to 1,200 seconds.
Questflow is a platform for creating autonomous AI "Clones" that aggregate onchain markets (Polymarket, Pump.fun, OKX, Opinion Labs, etc.) to discover alpha, execute trades, and generate revenue. This particular endpoint appears to be a developer/testnet instance — it runs on Base Sepolia rather than mainnet, and the agent's name and description are both simply "new creation," suggesting it may be a freshly created or template agent rather than a production-tuned one.
Documentation is extremely sparse. There is no OpenAPI spec, no dedicated docs page, and no detailed description of what this specific agent does beyond accepting a text message and returning a text response. The x402 challenge and outputSchema are the only technical references available. Prospective callers should treat this as an experimental/testnet endpoint.
Capabilities
Use cases
- —Sending natural-language queries to an autonomous AI agent and receiving text responses
- —Testing x402 micropayment flows against a live agent on Base Sepolia
- —Integrating Questflow swarm agents into automated pipelines via HTTP POST
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Testing agent-to-agent communication with micropayments on a testnet
- —Exploring Questflow's swarm agent infrastructure
Not for
- —Production workloads requiring mainnet payments and SLAs
- —Users needing detailed, documented API contracts or OpenAPI specs
- —Non-crypto use cases where standard API auth is preferred over x402
Quick start
curl -X POST https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68f893dc7aa0f71b3c5ec33e \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{"input": "Hello, what can you do?"}'Example
Request
{
"input": "Hello, what can you do?"
}Response
{
"response": "I can help you with various tasks. How can I assist you today?"
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and has a minimal outputSchema, but there is no OpenAPI spec, no documentation, no examples, and the agent name/description are generic placeholders ("new creation"). This is effectively a stub listing on a testnet.
Warnings
- —Running on Base Sepolia testnet — not suitable for production use
- —Agent name and description are both 'new creation', suggesting a template or placeholder
- —No API documentation, OpenAPI spec, or usage examples available from the provider
- —Response example is inferred from the outputSchema, not from an actual observed response
- —Maximum timeout of 1200 seconds suggests potentially long-running agent tasks
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base Sepolia with maxAmountRequired of 500000https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68f893dc7aa0f71b3c5ec33e
- —Questflow is a platform for creating AI Clones that aggregate onchain markets like Polymarket, Pump.fun, OKX, and Opinion Labshttps://api-dev.intra-tls2.dctx.link
- —The x402 challenge description states 'new creation | Powered by Questflow'https://api-dev.intra-tls2.dctx.link/x402/swarm/qrn:swarm:68f893dc7aa0f71b3c5ec33e