Public API · No API key required

Put my LoRAs directly into your workflows.

I built this API so you can search my catalog, get ready-to-use prompts and poses, show preview images, and download my LoRAs directly from ComfyUI extensions and personal tools.

Get started Try a live search

Checking API… Base URL: JSON responses No authentication

Quick start

Your first result in three steps

Most integrations only need search, LoRA details, and download. Everything else is optional.

Search

Find one of my LoRAs by character, series, style, trigger phrase, or ID.

Get workflow data

Request my artifact ID, base-model compatibility, trigger words, prompts, outfits, poses, and previews.

Install safely

Create a download session, verify the SHA-256, then save the file in a configured ComfyUI LoRA folder.

Example · Search for a LoRA

curl "/api/v1/loras/search?q=frieren&limit=5" \
  -H "Accept: application/json" \
  -H "X-KurutAI-Client: my-comfyui-extension/1.0"

Live playground

Try it without writing code

This sends a real request to my public catalog. Change the options and inspect the exact JSON I return to your extension.

Search LoRAs

GET /api/v1/loras/search

Live request

Run the search to see a response here.

Things to know

Simple defaults, predictable behavior

I keep the API public and intentionally low-friction. These conventions apply to every endpoint I provide.

Identify your extension

Send X-KurutAI-Client: name/version. I keep it optional, but it helps me diagnose errors and understand API usage.

Pagination uses cursors

Pass the returned nextCursor back as ?cursor=…. Do not build or modify cursors yourself.

I only expose public LoRAs

I never return private, offline, cancelled, or unavailable entries through my v1 catalog.

I keep limits generous

I do not want normal usage to be affected. My current ceilings per IP are 300 reads, 120 gallery/media requests, 60 compute requests, and 12 downloads per minute.

Errors have one shape

Check the HTTP status, then read error.code and error.message. Validation errors also include issues.

I optimize previews

Use small for search lists, card for detail views, and avoid full until a user opens an image.

Workflows keep stable IDs

Save loraId, artifact.id, and artifact.sha256. Resolve them when a workflow opens so you can clearly show whether an update is available.

Downloads follow ComfyUI actions

An extension may download after an Install click or when the user queues a workflow that needs the LoRA. It should never download merely because somebody opened a workflow.

Endpoint reference

Everything I make available

Open an endpoint to see the options I support and a copyable example.

Find an endpoint

No endpoints match that search.