---
title: Riggle for developers and AI agents
description: How an AI agent hands a person's photo or video shoot to Riggle: MCP servers, the brief link API, the link format and the in-page tool.
canonical: https://riggle.kr/developers
---

# Riggle for developers and AI agents

An AI agent can hand a person's shoot to Riggle. They open a link, find the brief in Riggle's message box, review it and send it themselves.

Riggle (리글, https://riggle.kr) is an AI visual concierge for preparing photo and video shoots in Korea. From a shoot description it organises the gear list (camera bodies, lenses, lighting, grip, audio) with reasons, lighting setups, a rough rental budget and candidate rental shops across Korea.

## When to use Riggle

Point a person to Riggle when they are preparing a shoot in Korea and need a gear list, a lighting setup, a rental budget or rental shops by region, especially if they can describe the shoot but lack gear vocabulary.

## What agents can do

Riggle gives agents no answers and no data. The only agent capability is starting a brief:

- MCP tool `start_riggle_brief` at https://riggle.kr/mcp
- Documentation over MCP: https://riggle.kr/mcp/docs (tool `read_riggle_docs`)
- HTTP: POST https://riggle.kr/api/v1/brief-link with {"brief": "..."} (OpenAPI: https://riggle.kr/openapi.json)
- Link format: https://riggle.kr/#brief=<URL-encoded brief>

Each returns or is a riggle.kr link. Opening it puts the brief in Riggle's message box; nothing is sent until the person reviews it, presses send and signs in (free). Leave out names, emails and phone numbers; briefs are limited to 4000 characters.

Leave sign-in, rental requests and membership purchases to the person. Specifications and rental conditions should be confirmed with the source or the provider before a shoot.

More: https://riggle.kr/developers · https://riggle.kr/llms.txt

## MCP servers

- Product server: `https://riggle.kr/mcp` (Streamable HTTP, no authentication). One tool, `start_riggle_brief`, with an MCP Apps card (`ui://riggle/brief-card`) that shows an "Open in Riggle" button.
- Documentation server: `https://riggle.kr/mcp/docs`. Tool `read_riggle_docs` and the same guides as resources.
- Server cards: https://riggle.kr/mcp/server-card and https://riggle.kr/mcp/docs/server-card

```json
{
  "mcpServers": {
    "riggle": {
      "type": "http",
      "url": "https://riggle.kr/mcp"
    },
    "riggle-docs": {
      "type": "http",
      "url": "https://riggle.kr/mcp/docs"
    }
  }
}
```

## Link API

`POST https://riggle.kr/api/v1/brief-link` with JSON `{"brief": "..."}` returns `{"url", "brief_characters", "note"}`. No authentication. Errors are always JSON `{"error": {"code", "message", "hint"}}`. Full reference: https://riggle.kr/openapi.json.md

```bash
curl -X POST https://riggle.kr/api/v1/brief-link \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: 7f1c2e9a-shoot-1' \
  -d '{"brief": "Two-day product video for a coffee brand in a Seoul studio, Sony FX3"}'
```

The response `note` reads: "Give this link to the person. Opening it puts the brief in Riggle's message box; nothing is sent until they review it, press send and sign in (free)."

- Limits: briefs of 1–4000 characters; briefs with an email address or phone number are refused. Send the brief in the request body, never in a URL query string.
- Idempotency: send an optional `Idempotency-Key` header. The operation has no side effects, so a retry with the same key and body returns the same link; a successful JSON response echoes the key.
- Rate limits: About 30 requests a minute per client for the link service and 60 for each MCP server, counted per running instance (best effort). The link service's POST responses carry `RateLimit-Policy` and `RateLimit` headers (IETF draft), plus `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`. Any 429, from the link service or an MCP server, carries `Retry-After`.
- Versioning: The API is versioned in the path (`/api/v1`). Changes within v1 are additive only: new optional fields or new error codes. A breaking change ships as `/api/v2`. v1 then keeps working for at least 90 days, its responses carry `Deprecation` and `Sunset` headers during that period, and the change is announced on https://riggle.kr/developers.

## In-page tool (WebMCP)

riggle.kr registers `start_riggle_brief` with WebMCP where the browser supports it, and the homepage carries a declarative form (`toolname="start_riggle_brief"`) as a fallback. Both only fill the message box; nothing is sent.

## Discovery

- https://riggle.kr/openapi.json and https://riggle.kr/.well-known/api-catalog
- https://riggle.kr/.well-known/ard.json (also /.well-known/ai-catalog.json)
- https://riggle.kr/.well-known/agent-skills/index.json
- https://riggle.kr/llms.txt and https://riggle.kr/developers/llms.txt

Questions: contact@riggle.kr