x402base-sepoliaquality 0.10

AI task planner that decomposes complex requests and delegates to specialized agents via x402.

Price
0.1 USDC / call
Protocol
x402
Verified
no

What it does

Questflow Tars is an AI task planner and coordinator exposed as an x402-payable endpoint. According to its listing description, it is designed to break down complex user requests into manageable steps and delegate those steps to specialized agents. The endpoint is identified by the resource name `qrn:copilot:tars` under the Questflow copilot namespace.

At the time of probing, the staging API server (`api-staging.intra-tls2.dctx.link`) returned HTTP 502 (Bad Gateway) on every path tested, including the root, `/docs`, `/api`, `/pricing`, and `/README`. No x402 payment challenge was returned, no OpenAPI schema was discovered, and no `agents.txt` or `ai-plugin.json` manifest was found. Consequently, almost all technical details—request/response schemas, pricing, authentication flow, and supported capabilities—remain unknown and cannot be verified.

Because the endpoint is currently unreachable and no documentation or schema is available, this listing is effectively a stub based solely on the existing title and description. Users should check back later or contact the Questflow team for status updates before attempting integration.

Capabilities

task-planningtask-decompositionagent-delegationmulti-agent-coordinationx402-payment

Use cases

  • Breaking down a complex user request into a sequence of subtasks
  • Coordinating multiple specialized AI agents to complete a workflow
  • Automating multi-step processes that require different domain expertise

Fit

Best for

  • Developers building multi-agent AI pipelines
  • Automating complex workflows that span multiple tools or domains
  • Users who need an AI coordinator to plan and delegate tasks

Not for

  • Production workloads requiring high availability (endpoint is currently down)
  • Use cases needing well-documented, schema-validated APIs

Quick start

# Endpoint is currently returning 502. When live, an x402 call would look like:
curl -X POST https://api-staging.intra-tls2.dctx.link/x402/copilot/qrn:copilot:tars \
  -H "Content-Type: application/json" \
  -d '{"prompt": "Plan and execute a market research report"}'

Endpoint

Transporthttp
Protocolx402
Pay to0x54fB0Ef420E403539CA5c47893C5BA0F97b6bF3C
CurrencyUSDC

Quality

0.10/ 1.00

The endpoint returns 502 on all paths. No schema, no documentation, no pricing, and no working x402 challenge were found. The listing is based entirely on the pre-existing title and description, making it a minimal stub.

Warnings

  • Endpoint returns HTTP 502 (Bad Gateway) — host server is down or misconfigured
  • No x402 payment challenge was returned; x402 protocol support is unverified
  • No OpenAPI schema, ai-plugin manifest, or agents.txt discovered
  • This is a staging URL (api-staging.*) and may not represent a production service
  • All capabilities and use cases are inferred from the title/description alone; none are verified

Citations

Provenance

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

Agent access