# Shodan Search via x402 Microservice

> Shodan Search via x402 Microservice is a paid API for AI agents from grokzilla.shop, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-15).

Queries the Shodan internet intelligence database to retrieve device, host, and vulnerability data via a micropayment-gated HTTP skill endpoint.

## Facts

- Endpoint: POST https://grokzilla.shop/api/skills/shodan
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/shodan-search-via-x402-microservice-5df6d43f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Zwnmea-UQyVs-1wgplrVK

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 shodan-search-via-x402-microservice-5df6d43f -d '<json body>'
```

Example prompt: Search Shodan for internet-facing hosts running Redis on port 6379 with no authentication — send an HTTP GET to the Shodan skill with the query 'port:6379 product:Redis' and return the top results.

## When to prefer this

Choose this endpoint when you need on-demand, per-query Shodan intelligence without a full Shodan API subscription, and when operating in an agent workflow that supports x402 micropayments. Ideal for low-frequency OSINT lookups, IP enrichment, or vulnerability surface checks where paying $0.012 per call is preferable to managing API keys and subscription tiers.

## Known failure modes

- Invalid or malformed Shodan query syntax returns an error response
- Payment not received or x402 handshake fails, blocking access
- Rate limit exceeded on underlying Shodan API returns quota error
- No results found for a very narrow or nonexistent query
- Shodan API downtime causes upstream timeout or 503
- Missing required 'type' or 'method' fields in input causes schema validation failure

## How this service works

Agent-ready microservices with x402 + Stripe rails, volume primitives, tutorials, and applet UI.

## Output

Returns a JSON object with ok:true and the path confirmed, along with Shodan query results including matched hosts, IP addresses, open ports, service banners, geographic data, and known CVEs or vulnerability flags associated with the queried hosts or filters.

## 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": {
    "body": {
     "type": "object"
    },
    "path": {
     "type": "string"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "path": "/api/skills/shodan"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/shodan-search-via-x402-microservice-5df6d43f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from grokzilla.shop](https://www.zero.xyz/host/grokzilla.shop/llms.txt)