x402basequality 0.78

Open a conversation thread with a service provider on the402.ai marketplace via x402 micropayment.

Price
0.001 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint opens a new conversation thread between an AI agent and a third-party service provider listed on the402.ai marketplace. It is part of the402.ai's Threads system, which supports negotiation, messaging, file uploads, price proposals, and payment acceptance before or instead of a direct fixed-price purchase. The endpoint accepts a POST request with an optional `brief` object (service-specific input data conforming to the service's input_schema) and an optional `message` string (initial message to the provider). It returns a `thread_id`, `status`, and `service_id`.

Payment is $0.001 USDC on Base (the x402 challenge confirms maxAmountRequired of 1000 base units with USDC at 6 decimals = $0.001). Payment can be made via the x402 protocol (X-PAYMENT header with a signed EIP-3009 authorization using the @coinbase/x402 SDK) or via a pre-funded balance (X-BALANCE-AUTH header after depositing via POST /v1/balance/deposit). The service ID is embedded in the URL path.

The402.ai is an open marketplace where AI agents discover and purchase data APIs, automated tools, and human-delivered services, all payable with USDC on Base L2. The thread/inquire flow is designed for services that require discussion or custom quotes before purchase — particularly human services like content writing, design, or SEO optimization. After opening a thread, agents can exchange messages, upload files, receive price proposals from providers, accept and pay, track delivery, verify results, or dispute.

Capabilities

x402-paymentusdc-on-baseconversation-threadservice-inquiryagent-marketplaceasync-negotiationfile-uploadprice-proposalescrow-payment

Use cases

  • An AI agent wants to discuss requirements with a human service provider before committing to a purchase
  • An agent needs a custom quote for a service listed as quote_required pricing model
  • An agent opens a thread to clarify deliverable specifications for a complex async service
  • An agent initiates negotiation on scope or timeline for a human-delivered project

Fit

Best for

  • AI agents that need to negotiate or clarify before purchasing human or complex services
  • Automated workflows that require pre-purchase communication with service providers
  • Agents operating on Base L2 with USDC wallets seeking human-in-the-loop services

Not for

  • Direct instant data API calls where no negotiation is needed (use /purchase instead)
  • Users without USDC on Base or an x402-compatible wallet
  • Non-agent human users looking for a traditional freelance marketplace UI

Quick start

curl -X POST https://api.the402.ai/v1/services/svc_cd3efb354cd24307/inquire \
  -H 'Content-Type: application/json' \
  -H 'X-PAYMENT: <signed-eip3009-authorization>' \
  -d '{"message": "I need a site audit for https://example.com"}'

Example

Request

{
  "brief": {
    "site_url": "https://example.com"
  },
  "message": "I need a full site audit including security, performance, and SEO. What is your turnaround time?"
}

Response

{
  "status": "open",
  "thread_id": "thr_abc123def456",
  "service_id": "svc_cd3efb354cd24307"
}

Endpoint

Transporthttp
Protocolx402
Pay to0x21bCE104282d6a089539C34aDddE152D42A02D0e
CurrencyUSD COIN

Quality

0.78/ 1.00

The endpoint is live (402 challenge captured), has a clear OpenAPI spec with input/output schema in the outputSchema field, documented pricing ($0.001 USDC), and the broader platform is well-described. Deducted points because response schemas in the OpenAPI are generic `type: object` without detailed properties, and the docs endpoint returns 404.

Warnings

  • The /docs endpoint returns 404 — no dedicated documentation page is available beyond the landing page and OpenAPI spec.
  • Response body schemas in the OpenAPI are all generic `type: object` — detailed field descriptions come only from the x402 challenge outputSchema.
  • The service ID svc_cd3efb354cd24307 in the URL is a specific service; the actual service behind it is unknown from the probe data alone.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:20:23Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access