canonical: https://jentic.com/apis/kodnextech.com/kodnextech

# Kodnextech NexWall Wallpaper REST API

The NexWall Wallpaper REST API serves phone-portrait HD wallpapers up to 4K, plus live video wallpapers on the Ultra plan, as JSON for wallpaper apps on Android, Flutter, iOS, React Native, web, and Python. Wallpapers can be listed and filtered by category, type, resolution, search term, and update date, sorted by newest, oldest, popular, or random, and fetched one at a time with image, thumbnail, dimension, tag, and license details. Which content a call returns depends on the key's plan: Free keys get non-premium images, Pro keys add premium categories, and Ultra keys add live wallpapers. A keyless demo endpoint returns Free-plan content for trying the API before registering.

## For AI agents

Browse, search, and fetch NexWall phone wallpapers by category, resolution, and type, with image and thumbnail URLs and license details for each result.

## Scope

Does not upload, edit, or resize images, and does not offer general stock photography. Use for reading NexWall phone and live wallpapers and their categories only.

## Capabilities

- List the wallpaper categories the current API key can access
- Search wallpapers by keyword with the search filter and sort by newest, oldest, popular, or random
- Filter wallpapers by category_id, resolution such as 4k, type image or live, and updated_since date
- Browse a single category's wallpapers page by page with up to 100 per page
- Fetch one wallpaper by id with its image_url, thumbnail_url, dimensions, tags, and license
- Try Free-plan wallpaper results through the keyless demo endpoint before registering for a key

## Use cases

### AI agent wallpaper picker

An assistant that helps users personalise their phone needs a reliable source of correctly sized wallpapers. Through Jentic the agent searches for 'find phone wallpapers', loads the NexWall wallpaper list operation, and passes a search term, resolution, and sort order while the NexWall API key is injected as a bearer token at call time. Each result carries an image URL, thumbnail URL, and aspect ratio the agent can show directly.

Example prompt: Call GET /wallpapers with search 'abstract', resolution '4k', sort 'popular', and per_page 10, then return the image_url and thumbnail_url of each result

### Wallpaper app category browsing

A mobile wallpaper app shows a category grid and lets users drill into one category. NexWall lists the categories the key can access, then pages through a single category's wallpapers with page and per_page parameters, filtered by type to show still images or live video wallpapers where the plan allows.

Example prompt: Call GET /categories, pick the first category id, then call GET `/categories/{categoryId}/wallpapers` with page 1, per_page 30, and type 'image'

### Syncing new wallpapers into an app library

Apps that cache wallpapers locally need only what changed. The wallpaper list accepts an updated_since date and sort order, so a nightly job can fetch wallpapers updated after its last run and store their image URLs, resolution, and license string.

Example prompt: Call GET /wallpapers with updated_since '2026-11-01', sort 'newest', and per_page 100, and record each id, image_url, and license

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/wallpapers` | List and filter accessible wallpapers |
| GET | `/wallpapers/{id}` | Get one wallpaper |
| GET | `/categories` | List accessible categories |
| GET | `/categories/{categoryId}/wallpapers` | List wallpapers in a category |
| GET | `/demo/wallpapers` | Try the API without a key |

## Key resources

- **Wallpapers** — Image or live wallpapers with image, thumbnail, resolution, tags, and license
- **Categories** — Wallpaper categories accessible to the key's plan

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/kodnextech.com/kodnextech/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 NexWall by hand means registering for a key, sending it as a bearer token, and handling plan-specific responses when a key asks for premium or live content it cannot access. Through Jentic you install once, import NexWall from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** NexWall puts the category id in the URL path (`/categories/{categoryId}/wallpapers`) and the wallpaper id in `/wallpapers/{id}`, so a rule can pin your agent to one category. Every operation is a read, so the agent cannot change anything on the account whichever operations you allow.
- **Credential handling:** Your NexWall 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 'find phone wallpapers' or 'list wallpaper categories', and Jentic returns the matching NexWall operation with its input schema, including the sort and type enums.

## Related APIs

- **Wallhaven** — Search a community wallpaper collection by tags and resolution
- **Pexels** — Free stock photos and videos
- **Pixabay** — Free images, illustrations, and videos
- **Unsplash** — High-resolution photography to supplement a wallpaper collection

## FAQ

### What authentication does the NexWall Wallpaper REST API use?

Per its OpenAPI spec, the NexWall API uses a bearer token: send your NexWall API key as `Authorization: Bearer YOUR_API_KEY`. The demo wallpapers endpoint needs no credential. Through Jentic the key is stored by your own instance and attached at call time, so it stays out of the agent's context.

### What are the rate limits for the NexWall Wallpaper REST API?

The OpenAPI spec states the limits per plan: Free keys get 100 requests/day and 60 requests/minute, Pro keys 10,000 requests/day and 180 requests/minute, and Ultra keys 50,000 requests/day and 300 requests/minute. The keyless demo endpoint is limited to 10 requests/minute and 30 requests/day per IP.

### Is the NexWall Wallpaper API free?

Yes, there is a Free plan with one API key, no credit card, and commercial use allowed, covering non-premium image wallpapers. Per the spec, Pro keys add premium image categories and Ultra keys add live video wallpapers, and every plan may be used in free or paid apps under the NexWall Developer API License.

### Is there a NexWall MCP server?

You don't need an MCP server to give your agent NexWall. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the wallpaper and category operations with their input schemas when it needs them.

### How do I search for wallpapers with NexWall through Jentic?

Search Jentic for 'find phone wallpapers', load the NexWall wallpaper list operation, and execute GET /wallpapers with a search term of 2 to 100 characters, plus optional resolution, type, and sort filters. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with NexWall?

Yes. Write a rule that allows only GET `/categories/7/wallpapers` and GET `/wallpapers/{id}`, and the agent can browse that one category and open individual wallpapers but cannot run open searches across the whole library. Every call it makes is logged.
