# Flarea developer API

Flarea is the shortest server-side path from "build a webinar or live showroom" to a working product. One authenticated POST /v1/showrooms creates the event, AI run of show, host studio, signup page, guest room, and viewer destination. Flarea operates the media, event, recording, storage, and reliability layers behind one stable contract.

Base URL: https://api.flarea.ai
Human docs: https://flarea.ai/developers
Full agent context: https://flarea.ai/llms-full.txt
OpenAPI 3.1 primary reference: https://api.flarea.ai/v1/openapi.json
OpenAPI 3.1 compatibility reference: https://api.flarea.ai/api/v1/openapi.json
SDK source: https://github.com/asafktz/webinar-show/tree/main/sdk/flarea-js
Signup and API key: https://flarea.ai/auth?mode=signup

## Agent quickstart

1. Ask the user for FLAREA_API_KEY or direct them to signup. Never invent a key and never put it in browser code.
2. Create one client per customer: POST /v1/clients {"name":"Acme","external_id":"your_customer_id"}.
3. Create a showroom: POST /v1/showrooms with title, brief, and client_id. Send Authorization: Bearer, Content-Type: application/json, and Idempotency-Key.
4. Persist data.showroom.slug, links, meta.request_id, and the client mapping.
5. Retry only retryable failures and reuse the same Idempotency-Key for the same mutation.
6. Read GET /v1/usage for cost/error attribution.

There is no anonymous/free sandbox. All live examples require a valid key and are metered.

## Additive /v1 facade

- GET/POST /v1/clients
- GET/PATCH /v1/clients/{id}
- GET/POST /v1/showrooms
- POST /v1/examples/run {"example":"showroom", ...}
- GET /v1/usage?days=30

Existing /api/v1/** operations and @showrunner/sdk remain backward compatible.