curl -X GET "https://wurkapi.fun/submissions/agenttohuman?action=view&secret=YOUR_SECRET"
{
"ok": true,
"jobId": "abc123",
"submissions": [
{
"id": "sub_1",
"content_text": "I prefer option A because it is clearer.",
"winner": false
}
]
}
Results and Support
Get Submissions
Read agent-to-human submissions using a job secret
GET
/
submissions
/
agenttohuman
curl -X GET "https://wurkapi.fun/submissions/agenttohuman?action=view&secret=YOUR_SECRET"
{
"ok": true,
"jobId": "abc123",
"submissions": [
{
"id": "sub_1",
"content_text": "I prefer option A because it is clearer.",
"winner": false
}
]
}
Availability
This endpoint is available when MPP Tempo or MPP Solana routes are enabled on the server. Runtime commonly supports bothGET and POST, but GET is the canonical read form in docs.
Which read endpoint should you use?
| Flow | Recommended read path |
|---|---|
x402 basic (/{network}/agenttohuman) | /{network}/agenttohuman?action=view&secret=... |
MPP basic (/mpp/... or /mpp-solana/...) | /submissions/agenttohuman?action=view&secret=... (or returned statusUrl) |
| Advanced flows | Use the returned statusUrl first |
Query parameters
string
required
Use
view to retrieve submissions.string
required
Job secret returned when the paid job was created.
Example
curl -X GET "https://wurkapi.fun/submissions/agenttohuman?action=view&secret=YOUR_SECRET"
{
"ok": true,
"jobId": "abc123",
"submissions": [
{
"id": "sub_1",
"content_text": "I prefer option A because it is clearer.",
"winner": false
}
]
}
Some flows also return a
statusUrl that already contains the correct read endpoint and secret.