canonical: https://jentic.com/apis/wallhaven.cc/wallhaven-cc

# Wallhaven Cc Wallhaven API

The Wallhaven API provides access to the Wallhaven wallpaper platform. Search and browse high-quality wallpapers, view tags, manage collections, and access user settings. Rate limited to 45 requests per minute. The API exposes 7 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get wallpaper information, search wallpapers. Covers 7 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get wallpaper information
- Search wallpapers
- Integrate Wallhaven API into automated workflows
- Query and filter Wallhaven API records by parameters
- Monitor Wallhaven API operational status and events

## Use cases

### Developer Tools Operations

Use the Wallhaven API to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including get wallpaper information, search wallpapers, get tag information.

Example prompt: Call GET `/w/{id}` to get wallpaper information

### Automated Wallpapers Management

Automate wallpapers operations by combining multiple Wallhaven API endpoints. Agents can search wallpapers and then get tag information in a single workflow.

Example prompt: Call GET /search to search wallpapers, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wallhaven API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get wallpaper information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/w/{id}` | Get wallpaper information |
| GET | `/search` | Search wallpapers |
| GET | `/tag/{id}` | Get tag information |
| GET | `/settings` | Get user settings |
| GET | `/collections` | Get authenticated user's collections |
| GET | `/collections/{username}` | Get user's public collections |
| GET | `/collections/{username}/{id}` | Get wallpapers in a collection |

## Key resources

- **Wallpapers** — Wallpaper browsing and search
- **Tags** — Tag information
- **User** — User settings and collections
- **Collections** — User wallpaper collections

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 33 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/wallhaven.cc/wallhaven-cc/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Wallhaven API by hand means passing your key via the X-API-Key header or apikey query parameter on the wallhaven.cc/api/v1 host and attaching it to every request yourself. Through Jentic you install once, import the Wallhaven API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Wallhaven API puts the resource id in the URL path (`/w/{id}` and `/collections/{username}/{id}`), so a rule can pin your agent to one wallpaper or collection. Its operations are read-only, so you choose which reads the agent may call and it can retrieve wallpaper and collection data and nothing beyond that.
- **Credential handling:** Your Wallhaven API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get wallpaper information' or 'search wallpapers by tag', and Jentic returns the matching Wallhaven API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Wallhaven API use?

The Wallhaven API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get wallpaper information with the Wallhaven API?

Yes. Use the GET `/w/{id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wallhaven API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get wallpaper information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get wallpaper information'. Jentic returns the matching Wallhaven API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wallhaven API have?

The Wallhaven API exposes 7 endpoints covering wallpapers, tags, user operations.

### Can I limit what my agent is allowed to do with the Wallhaven API?

Yes. Because Jentic One is self-hosted and runs under your own rules, you decide which Wallhaven API operations your agent may call and which credentials it uses. The Wallhaven API is read-only, so you can allow only the reads you want, such as GET `/w/{id}` or GET /search, and keep everything else off. Since the resource id sits in the URL path for GET `/w/{id}` and GET `/collections/{username}/{id}`, you can also pin the agent to a single wallpaper or collection.