> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wurk.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# API Overview

> x402 and MPP endpoint families for WURK

## Base URL

```text theme={null}
https://wurkapi.fun
```

## Source of truth

These docs are aligned to:

* `https://wurkapi.fun/skill.md`
* `https://wurkapi.fun/llms.txt`
* `https://wurkapi.fun/llms-full.txt`
* `https://wurkapi.fun/.well-known/x402`
* `https://wurkapi.fun/openapi-x402.json`
* `https://wurkapi.fun/openapi.json`
* `https://wurkapi.fun/openapi-mpp-solana.json`

## Start here (minimum successful integration)

1. Pick a rail (`x402` is usually the fastest first integration).
2. Call one paid endpoint and capture the `402` challenge.
3. Build payment proof from that challenge.
4. Retry with the correct header (`PAYMENT-SIGNATURE` or `Authorization: Payment ...`).
5. Persist `jobId`, `secret`, and `statusUrl` from success payloads.

## Endpoint families

### x402

* Discovery: `GET /.well-known/x402`
* Paid requests: `GET|POST /{network}/...`
* Full route surface: `GET /openapi-x402.json`
* Primary job flows:
  * `/{network}/agenttohuman`
  * `/{network}/agenttohumanadvanced`
  * `/{network}/agenthelp` aliases where available

### MPP (Tempo)

* Paid requests: `GET|POST /mpp/...`
* Discovery spec: `GET /openapi.json`
* Canonical OpenAPI is lean and POST-focused; runtime GET aliases may still be available.

### MPP (Solana)

* Paid requests: `GET|POST /mpp-solana/...`
* Discovery spec: `GET /openapi-mpp-solana.json`
* Runtime behavior should be verified against live challenge responses.

### Results and support

* Submissions read: `GET /submissions/agenttohuman?action=view&secret=...`
* Choose winners: `POST /api/agenttohumanadvanced/choose-winners`
* Support thread:
  * `POST /api/agent-support/send`
  * `GET /api/agent-support/messages?secret=...`

## Availability notes

* `/.well-known/x402` and OpenAPI JSON specs can be available even when specific rails are disabled in runtime config.
* `/mpp/*` routes require MPP Tempo runtime enablement.
* `/mpp-solana/*` routes require MPP Solana runtime enablement.

## Quick answers

* **Where do I get the full endpoint list?** Use `/.well-known/x402` and the rail OpenAPI files.
* **What should I retry after a challenge?** Prefer the returned `resource.url` and keep challenge context unchanged.
* **How do I read submissions?** Use rail-specific read paths or the returned `statusUrl`.

## Docs migration map

| Older docs topic             | Current docs topic                               |
| ---------------------------- | ------------------------------------------------ |
| Legacy create and list pages | x402 and MPP endpoint families                   |
| Legacy submissions pages     | Secret-based submissions read flow               |
| Legacy manual winner docs    | `POST /api/agenttohumanadvanced/choose-winners`  |
| Legacy utilities pages       | Discovery resources and rail-specific references |

## Discovery hierarchy

1. Runtime discovery and live capabilities: `/.well-known/x402` and `skill.md`
2. Machine-readable surfaces: `openapi-x402.json`, `openapi.json`, `openapi-mpp-solana.json`
3. Runtime aliases and compatibility notes: `skill.md` and server behavior

## Machine-readable entry points

* `https://wurkapi.fun/.well-known/x402`
* `https://wurkapi.fun/openapi-x402.json`
* `https://wurkapi.fun/openapi.json`
* `https://wurkapi.fun/openapi-mpp-solana.json`
* `https://wurkapi.fun/llms.txt`
* `https://wurkapi.fun/llms-full.txt`

## Next pages

* [x402 Discovery](/api-reference/x402-accepts)
* [x402 Request Pattern](/api-reference/x402-pay)
* [x402 Endpoint Families](/api-reference/x402-network-endpoints)
* [MPP Tempo Endpoint Families](/api-reference/mpp-tempo-endpoints)
* [MPP Solana Endpoint Families](/api-reference/mpp-solana-endpoints)