# Battleship Command - Bomb Attack

> Battleship Command - Bomb Attack is a paid API for AI agents from battleship.nanupanda.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Purchases a bomb attack on a specific grid coordinate in an on-chain battleship game, returning hit/miss/sunk result and potential prize pool rewards.

## Facts

- Endpoint: POST https://battleship.nanupanda.com/api/bomb
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/battleship-command-bomb-attack-1548d548
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LBgx9YFRerAQpHZJFcpmp

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 battleship-command-bomb-attack-1548d548 -d '<json body>'
```

Example prompt: Attack coordinate (14, 22) in the battleship game for me — spend the 0.10 USDC to drop a bomb there and tell me if it's a hit, miss, or sunk.

## When to prefer this

Use this endpoint when an agent needs to make a paid move in the on-chain battleship game at nanupanda.com, specifically to bomb a grid coordinate and retrieve the attack outcome. Prefer over reading game state (which is a GET endpoint) when the goal is to actually play/attack.

## Known failure modes

- Invalid coordinates outside 0-29 range returns error
- Insufficient or missing USDC payment via X-PAYMENT header returns 402
- Already-bombed coordinate may return error or miss
- Network or blockchain congestion may cause timeout
- Invalid payment header format returns 400

## How this service works

Purchase a bomb attack on a specific coordinate in the battleship game. Each bomb costs 0.10 USDC and can result in a hit, miss, or sinking a ship. Successful attacks may earn rewards from the prize pool. Send coordinates {x, y} in POST body with X-PAYMENT header. View current game state at https://battleship.nanupanda.com//api/game/state

## Output

Returns whether the attack was a hit, miss, or sunk a ship; a descriptive message; the attacked coordinates; the bomber's address; and the payment transaction hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "x",
  "y"
 ],
 "properties": {
  "x": {
   "type": "integer",
   "description": "X coordinate (0-29) for bomb attack"
  },
  "y": {
   "type": "integer",
   "description": "Y coordinate (0-29) for bomb attack"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "result": {
  "enum": [
   "hit",
   "miss",
   "sunk"
  ],
  "type": "string",
  "description": "Attack result"
 },
 "message": {
  "type": "string",
  "description": "Descriptive message about the attack"
 },
 "success": {
  "type": "boolean",
  "description": "Whether the attack was successful"
 },
 "coordinates": {
  "type": "object",
  "description": "Attacked coordinates {x, y}"
 },
 "bomberAddress": {
  "type": "string",
  "description": "Address of the attacking player"
 },
 "transactionHash": {
  "type": "string",
  "description": "Payment transaction hash"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/battleship-command-bomb-attack-1548d548/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from battleship.nanupanda.com](https://www.zero.xyz/host/battleship.nanupanda.com/llms.txt)
