# JP Data API – Anime Search

> JP Data API – Anime Search is a paid API for AI agents from jp-data-api-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Search for anime titles and related information by keyword query

## Facts

- Endpoint: GET https://jp-data-api-production.up.railway.app/anime/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jp-data-api-anime-search-fa467305
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ILM98TaLIrfolWznjgIEx

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 jp-data-api-anime-search-fa467305
```

Example prompt: Can you search for anime related to 'Attack on Titan' and tell me what comes up?

## When to prefer this

Use this endpoint when you need to search for anime titles or metadata by keyword within a broader JP Data API workflow, especially when already using other JP Data API endpoints (EDINET, JMA, holidays, FX) and want a consistent single provider. Best for lightweight keyword-based anime lookup at low cost ($0.01 USDC per call).

## Known failure modes

- Missing required 'q' query parameter returns a 400 error
- No results found for obscure or misspelled titles returns empty results array
- Payment not provided or invalid returns HTTP 402 with payment requirements
- Network timeout from upstream anime data source

## How this service works

Japanese data for AI agents: corporate disclosures (EDINET), earthquakes (JMA), holidays, FX, address and text utilities. USDC on Base.

## Output

Returns a JSON object containing anime search results matching the provided keyword query, including relevant metadata about matching anime titles.

## 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",
     "required": [
      "q"
     ],
     "properties": {
      "q": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jp-data-api-anime-search-fa467305/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-data-api-production.up.railway.app](https://www.zero.xyz/host/jp-data-api-production.up.railway.app/llms.txt)