# shop.northheart.app Debug Fail Endpoint

> shop.northheart.app Debug Fail Endpoint is a paid API for AI agents from shop.northheart.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-20).

Intentionally fails after a successful payment to let developers test how their x402 payment client handles various error and edge-case responses

## Facts

- Endpoint: POST https://shop.northheart.app/debug/fail?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/shop-northheart-app-debug-fail-endpoint-f03c3ea6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pVYgTGxnw2c5FYKkzNOb2

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 shop-northheart-app-debug-fail-endpoint-f03c3ea6 -d '<json body>'
```

Example prompt: Trigger a 500 error on purpose using the debug fail endpoint — I want to see how my x402 payment client handles an internal server error after a successful payment goes through.

## When to prefer this

Use this endpoint when you need to verify your x402 payment client or AI agent can gracefully handle a range of post-payment server failures. It is ideal during development and integration testing before going live against real paid endpoints, since it guarantees a specific failure type on demand without relying on real outages.

## Known failure modes

- Omitting the mode parameter may result in undefined behavior or a default error
- Invalid mode values not in the enum are ignored or produce unexpected results
- Payment may still be deducted even if the request is malformed
- Network timeout if using mode=big with very large payloads

## How this service works

Fail on purpose, after payment, so you can test how your program copes: ?mode=empty|big|error500|error429|error503

## Output

Returns one of five intentional failure responses depending on the mode parameter: an empty body (mode=empty), an oversized payload (mode=big), an HTTP 500 Internal Server Error (mode=error500), an HTTP 429 Too Many Requests (mode=error429), or an HTTP 503 Service Unavailable (mode=error503). The payment is deducted regardless of the error response returned.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "mode"
     ],
     "properties": {
      "mode": {
       "enum": [
        "empty",
        "big",
        "error500",
        "error429",
        "error503"
       ],
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "mode": {
       "type": "string"
      },
      "note": {
       "type": "string"
      },
      "error": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/shop-northheart-app-debug-fail-endpoint-f03c3ea6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from shop.northheart.app](https://www.zero.xyz/host/shop.northheart.app/llms.txt)
