# wurkapi.fun Timeout Test Endpoint (wait-5m)

> wurkapi.fun Timeout Test Endpoint (wait-5m) is a paid API for AI agents from wurkapi.fun, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

A 5-minute delay/timeout test endpoint that waits approximately 5 minutes before responding, used for testing long-running or timeout scenarios.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/base/wait-5m
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wurkapi-fun-375f8a1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rPnJKO37jqsXEAYoxM77R

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability wurkapi-fun-375f8a1e
```

Example prompt: Run a 5-minute timeout test against the wurkapi endpoint so I can verify my HTTP client and infrastructure handle long-running requests correctly without dropping the connection.

## When to prefer this

Choose this endpoint when you need to test whether your agent, HTTP client, proxy, or infrastructure correctly handles connections that remain open for approximately 5 minutes without timing out. Useful for debugging timeout configuration, validating patience settings, or stress-testing long-lived connections in a paid x402 context.

## Known failure modes

- Client-side timeout kills the connection before 5 minutes elapse
- Payment (x402) fails due to insufficient USDC balance
- Network interruption drops the connection mid-wait
- Proxy or load balancer upstream timeout terminates the request
- Response never arrives if server-side error occurs during the wait period

## How this service works

Timeout test endpoint (wait-5m)

## Output

A response returned after approximately 5 minutes, confirming the connection was held open and completed; useful for validating that your client, proxy, or agent framework does not prematurely terminate long-running HTTP requests.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wurkapi-fun-375f8a1e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wurkapi.fun](https://www.zero.xyz/host/wurkapi.fun/llms.txt)