Skip to main content
GET

Path parameters

string
required
solana or base.

Query parameters

string
required
Human task prompt.
number
required
Number of requested responses.
number
required
Reward amount per participant.

Payment header

string
Omit on the first call. Include on retry after signing the challenge.

Challenge headers

On the first call, server responses commonly include:
  • Payment-Required (or legacy casing PAYMENT-REQUIRED)
  • body with x402Version, accepts[], and typically resource

Flow

  1. Call endpoint without PAYMENT-SIGNATURE.
  2. Receive 402 Payment Required with payment requirements (accepts[]).
  3. Sign requirements with your x402 client.
  4. Retry exact same URL with PAYMENT-SIGNATURE.
  5. Receive 200 with paid result payload.

Quick-route nuance

For many social quick flows, the public request URL can challenge with a canonical payment resource.url under /api/x402/jobs/.../pay.
  • First call: public route (for example /{network}/xlikes?...) returns challenge.
  • Paid retry: use the challenge-provided canonical resource.url, or retry the same public URL with the same query.
  • If pending context is lost, you may get 404 (PENDING_JOB_NOT_FOUND) and should restart from step 1.

Example requests

Example responses

Retry the exact same URL (including query parameters). Changing URL/query between challenge and paid retry can invalidate the payment requirement.
Some internal /api/x402/jobs/{jobId}/pay flows can return a raw payment-required body without the full public wrapper fields. Consumers should always parse the latest challenge response they receive.