# API Specification Draft Sample

## Input snapshot

Customers need to fetch saved outputs by module, read recent runs, and trigger exports from internal tools. The API needs per-user auth, workspace scoping, API key access for backend clients, and conservative export rate limits.

## Output snapshot

### Endpoint List

- `GET /saved-outputs`
- `GET /saved-outputs/{id}`
- `GET /generations/recent`
- `POST /exports/{savedOutputId}`

### Auth Model

Use API key auth for backend clients and enforce user-or-workspace ownership checks on every resource lookup.

### Why this sample matters

This example shows how product and engineering notes become a reviewable API draft before implementation starts.
