Fortune Fog API Docs

Public-safe Phase 1 · 220 public fortunes · 6 categories · 8 tones

Fortune Fog exposes deterministic fortune generation, goal-oriented reflection, public quote/library access, honest model-degraded endpoints, and JSON-RPC MCP tooling. Public-safe endpoints do not require an API key. Future protected actions use PLATPHORM_API_KEY only when PLATPHORM_REQUIRE_API_KEY=true.

Endpoints

GET /api/health public-safe
GET /api/v1/health public-safe
GET /api/v1/fortune public-safe
POST /api/v1/fortune/reveal public-safe
POST /api/v1/fortune/deterministic public-safe
POST /api/v1/fortune/goal public-safe
GET /api/v1/fortune/categories public-safe
GET /api/v1/fortune/tones public-safe
GET /api/v1/quotes public-safe
POST /api/v1/share-card public-safe degraded server renderer
POST /api/v1/export public-safe
POST /api/v1/model/fortune future protected when enforcement enabled
POST /api/v1/model/share-copy future protected when enforcement enabled
GET /api/mcp public-safe introspection
POST /api/mcp public-safe bounded JSON-RPC tools

Discovery

OpenAPI YAML · OpenAPI JSON · llms.txt · llms-index.json · MCP metadata

Boundary

Public-safe fortune reveal, deterministic fortune generation, goal-oriented reflective prompts, local non-sensitive favorites/history, read-only MCP introspection, RSS/feed consumption, trusted-domain discovery, standard route compliance, Vercel metadata capture, backend model scaffolding, and trace-linked Fortune operations are intentionally supported for public playful and reflective use. Fortune does not predict the future and does not provide medical, legal, financial, or crisis advice. PLATPHORM_API_KEY support is scaffolded for future protected backend services, protected model calls, share-card rendering, sync, test-triggering, reporting, administrative actions, and sensitive operations.