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

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

A test endpoint that waits approximately 1 minute before responding, used to simulate or test timeout behavior in API clients and agents.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/base/wait-1m?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wurkapi-fun-cb2755b5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0mzGN3hhVKkQ2Uup3kSIL

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-cb2755b5
```

Example prompt: Can you call the 1-minute timeout test endpoint on wurkapi.fun to check if our HTTP client and retry logic handle long-running requests properly?

## When to prefer this

Use this endpoint when you need to test how an API client, agent framework, or workflow handles slow or delayed HTTP responses. Specifically useful for validating timeout configurations, retry policies, and long-poll handling in systems that use x402 micropayments.

## Known failure modes

- Client-side timeout before the 1-minute wait completes — client receives a connection timeout error
- Payment failure via x402 — 402 Payment Required returned if USDC payment is not provided
- Network interruption during the wait period — connection reset or dropped
- Server-side error after payment but before response — 500 error with no body

## How this service works

Timeout test endpoint (wait-1m)

## Output

A response returned after approximately 1 minute of waiting, confirming the endpoint processed the request successfully after the delay. Useful for validating timeout handling, retry logic, and long-poll behavior in API clients.

## 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-cb2755b5/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)