Anikoto API

A high-performance REST API for scraping anime data from anikoto.net, built with Next.js 16

Author: Teramoto

Features • Quick Start • API Endpoints • Project Structure • Deployment

For educational purposes only. This project is not affiliated with anikoto.net.

Important

1. There was previously a hosted version of this API for showcasing purposes only, and it was misused; It is recommended to deploy your own instance for personal use by customizing the API as you need it to be.
2. This API is just an unofficial API for anikoto.net and is in no other way officially related to the same.
3. The content that this API provides is not mine, nor is it hosted by me. These belong to their respective owners. This API just demonstrates how to build an API that scrapes websites and uses their content.

---

✨ Features

• 15 REST endpoints covering home, search, filter, anime detail, episodes, related, recommendations, tooltip, schedule, streaming sources (with opening/ending skip ranges), and a streaming proxy
• High-Volume Proxy Engine: Zero-copy ReadableStream video proxying, multi-node outbound proxy pool routing (PROXIES / PROXY_LIST), SSRF protection, anti-bot browser header rotation, and exponential backoff retries.
• Response envelope — every response is { ok: true, data: ... } or { ok: false, message: "..." }
• In-memory cache (TTL per endpoint) — add ?refresh=1 to any request to bypass
• Interactive Swagger UI docs at / powered by an OpenAPI 3.0 spec (public/openapi.yaml)
• TypeScript — fully typed responses via src/lib/types.ts

---

🚀 Getting Started

# Install dependencies
npm install

# Start dev server
npm run dev

Open http://localhost:3000 to see the interactive API docs.

---

📖 API Overview

Method	Endpoint	Description
GET	/api/home	Home data: spotlight, latest eps, top anime
GET	/api/search?keyword=&page=	Search anime by keyword (paginated)
GET	/api/filter	Advanced multi-param filter (paginated, returns results & optional topRated)
GET	/api/anime/:slug	Anime detail info (without related or recommendations)
GET	/api/anime/:slug/episodes	Episode list (with range filter)
GET	/api/anime/:slug/related	Related anime (watch order/sequels/prequels)
GET	/api/anime/:slug/recommendations	Recommended anime list (cards)
GET	/api/anime/tooltip/:id	Anime tooltip / preview info (by poster's data-tip ID)
GET	/api/updated?page=	Paginated latest updated anime listing directly from https://anikoto.net/latest-updated (returns results & optional topRated)
GET	/api/widget?name=&page=	Home AJAX widgets: updated-all, updated-sub, updated-dub, trending, random
GET	/api/status?type=&page=	Airing status listing: currently-airing, finished-airing, not-yet-aired (returns results & optional topRated)
GET	/api/genre/:genre?page=	Browse by genre slug (returns results & optional topRated)
GET	/api/type/:type?page=	Browse by media type: tv, movie, ova, ona, special, music (returns results & optional topRated)
GET	/api/schedule?tz=&images=	Weekly airing schedule (optional UTC tz offset in hours and image resolution)
GET	/api/watch/:slug?ep=	Streaming sources (m3u8, subtitles, and opening/ending skip ranges)
GET	/api/proxy?url=	High-volume streaming proxy (CORS bypass, zero-copy streaming, proxy routing)

See the full interactive documentation at / (when running locally) or in public/openapi.yaml.

---

⚡ Cache TTL

Endpoint	TTL
/api/home	5 minutes
/api/anime/:slug / /api/anime/tooltip/:id	30 minutes
/api/search	2 minutes
/api/filter	5 minutes
/api/schedule	1 hour
Episodes	10 minutes

Add ?refresh=1 to force a fresh scrape.

Tip

Schedule Images: By default, /api/schedule returns an empty string for anime images to keep response times fast (fetching schedule images requires visiting each anime details page). Setting images=true will concurrently fetch the poster images for all listed anime with a global concurrency limit of 5.

---

---

⚙️ Environment Variables

Configure environment variables in a .env file at the root directory:

# Target base URL (default: https://anikoto.net)
BASE_URL=https://anikoto.net

# Optional: CORS allowed origins (default: "*")
# Supports single origin, comma-separated list, or wildcard "*"
CORS_ALLOWED_ORIGIN=http://localhost:3000,https://your-app.vercel.app

# Optional: Cloudflare Worker URL for streaming proxy
CF_WORKER_URL=https://your-worker-name.workers.dev

# Optional: Comma-separated list of HTTP/HTTPS/SOCKS proxies for outbound routing
PROXIES=http://user:pass@node1.proxy.com:8080,http://node2.proxy.com:8080

---

☁️ Cloudflare Worker Proxy (Optional)

By default, the API provides an internal streaming proxy at /api/proxy to bypass CORS. For better performance and free unlimited bandwidth (100k req/day free tier), you can deploy the included Cloudflare Worker and configure the API to use it automatically.

1. Deploy the worker from the cloudflare-worker/ directory:

   cd cloudflare-worker
   npm install wrangler -g
   wrangler deploy

2. Add your worker URL as an environment variable in a .env file at the root of the project:

   CF_WORKER_URL=https://your-worker-name.workers.dev

   Note: When this environment variable is set, the /api/watch endpoint will automatically return proxy URLs pointing to your Cloudflare Worker instead of the internal /api/proxy.
3. (Optional) Configure outbound proxy rotation for Cloudflare Worker:

   npx wrangler secret put PROXIES
   # Enter comma-separated proxy list: http://user:pass@node1:8080,http://node2:8080

---

🗂️ Project Structure

src/
├── proxy.ts              # CORS & proxy middleware (Next.js 16)
├── app/
│   ├── page.tsx          # Swagger UI documentation page
│   ├── layout.tsx        # Root layout
│   └── api/              # API route handlers
│       ├── home/         # GET /api/home
│       ├── search/       # GET /api/search
│       ├── filter/       # GET /api/filter
│       ├── anime/        # GET /api/anime/:slug (+ /episodes)
│       │   └── tooltip/  # GET /api/anime/tooltip/:id
│       ├── updated/      # GET /api/updated
│       ├── status/       # GET /api/status
│       ├── genre/        # GET /api/genre/:genre
│       ├── type/         # GET /api/type/:type
│       ├── schedule/     # GET /api/schedule
│       ├── watch/        # GET /api/watch/:slug
│       └── proxy/        # GET /api/proxy
├── lib/
│   ├── proxy-pool.ts     # Proxy pool manager & SSRF guard
│   ├── types.ts          # TypeScript interfaces
│   ├── constants.ts      # Base URL, cache TTLs, filter options
│   ├── cache.ts          # Node-Cache instance
│   ├── fetcher.ts        # Axios & proxy pool based HTML fetcher
│   ├── extractors.ts     # Cheerio extraction helpers
│   └── scrapers/         # Per-endpoint scraping logic
│       ├── anime.scraper.ts
│       ├── home.scraper.ts
│       ├── schedule.scraper.ts
│       ├── search.scraper.ts
│       ├── tooltip.scraper.ts
│       └── watch.scraper.ts
public/
└── openapi.yaml          # OpenAPI 3.0 specification

---

🛠️ Tech Stack

• Next.js 16 — App Router
• Cheerio — server-side HTML parsing
• Axios — HTTP client
• Node-Cache — in-memory caching
• Swagger UI — interactive API docs

---

👤 Author

Teramoto · github.com/Teramoto669