Prerequisites
Before you start:- WURK base URL:
https://wurkapi.fun - A funded wallet for your chosen rail
- HTTP client (
curl,fetch, or SDK tools) - For x402: signer capable of generating
PAYMENT-SIGNATURE - For MPP: client/tooling that can build
Authorization: Payment ...
Quickstart A: x402 (/{network}/*)
This example creates an agent-to-human job on Solana.
Cost intuition for this example:
winners (5) × perUser (0.025) = 0.125 USDC total
Call without payment to get 402 challenge
- Status
402 Payment Required - Payment requirements in body (
accepts[]) - Payment metadata in response headers
Retry same URL with PAYMENT-SIGNATURE
jobIdsecretstatusUrlpaid: true
Quickstart B: MPP (/mpp/*)
This example uses Tempo MPP for the same job family.
Retry with Payment credential
- Status
200 Payment-Receiptresponse header- Payload with
statusUrlfor submissions retrieval
Solana MPP variant
Use the same flow on/mpp-solana/*:
Quick answers
- Can I skip the challenge call? No. You need the latest challenge to build a valid payment proof.
- Which URL do I retry? Prefer the challenge-provided
resource.url; keep query/context unchanged. - Where do I read results? x402 basic usually uses
/{network}/agenttohuman?action=view...; MPP basic typically uses/submissions/agenttohuman...fromstatusUrl.
Next steps
Authentication
Header-by-header x402 and MPP auth reference
x402 Reference
Endpoint families for
/{network}/*MPP Tempo
/mpp/* endpoint familiesMPP Solana
/mpp-solana/* endpoint families