# x402.shizu.me Bounty Cancel

> x402.shizu.me Bounty Cancel is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-22).

Cancels an open or stale-claimed bounty and refunds the full reward to the poster with no fee

## Facts

- Endpoint: POST https://x402.shizu.me/bounty/cancel?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-shizu-me-bounty-cancel-85587bf8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_q9Ysi4cLB0ba3D75ASaRn

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 x402-shizu-me-bounty-cancel-85587bf8 -d '<json body>'
```

Example prompt: Cancel my bounty with ID b-9f3a2c and refund the full reward back to me — nobody completed it and the claimer stopped responding past the deadline.

## When to prefer this

Use this endpoint when you are the bounty poster and want to fully cancel and reclaim your reward from a bounty that is either still OPEN (no claimer) or in a CLAIMED state where the claimer has gone past the claim TTL without submitting a result. Do not use this if a result has already been SUBMITTED — in that case use the approve/reject flow instead. This endpoint charges no fee and issues a full refund.

## Known failure modes

- Bounty ID not found — returns 404 or error if the ID does not exist
- Caller is not the original poster — returns authorization error
- Bounty is in SUBMITTED state — cannot cancel once a result is submitted; must approve or reject instead
- Bounty is already cancelled or resolved — returns conflict or idempotency error
- Claimer's TTL has not yet expired — cannot cancel a CLAIMED bounty until the stale threshold is passed
- Payment or on-chain refund failure — network or protocol error during fund return

## How this service works

Poster reclaims the reward of a bounty nobody completed: POST {id}. Full refund, no fee. Poster-only. Works while OPEN, or while CLAIMED-but-stale (the claimer ghosted past the claim TTL). Not once a result is SUBMITTED — approve that instead.

## Output

A confirmation that the bounty has been cancelled and the full reward refunded to the original poster, with no deducted fee. Typically includes the bounty ID, final status, and refunded amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {}
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "Xy1…",
  "state": "cancelled",
  "refunded_credits": 20
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-shizu-me-bounty-cancel-85587bf8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)