Minglyph
MINGLYPH API / PREVIEW

Meaningful type,
from one request.

Bring Minglyph’s readable, meaning-led artwork into your own product. One request carries the exact text, its idea, and the visual rule allowed to change.

CREATE A GENERATIONREST / JSON
curl https://minglyph.com/v1/generations \
  -H "Authorization: Bearer mg_live_…" \
  -H "Idempotency-Key: launch-001" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "PLAY",
    "meaning": "every letter finds its own way to move",
    "format": "doodle",
    "style": "letter-variant"
  }'
ACCEPTED / 202{ "id": "gen_01J…", "status": "queued", "credits_reserved": 4, "reused": false }
V1 / RESTPrivate by defaultIdempotent writesWorkspace-scoped reuse

Two headers. One clear brief.

Use a workspace API key and an idempotency key for every write. Keys are never exposed in generated assets.

HEADERAuthorization: Bearer mg_live_…
HEADERIdempotency-Key: launch-001
Authentication

Bearer keys bind every request, asset, and credit entry to one workspace.

A deliberately small surface.

GET/v1/styles

List the active visual recipes.

POST/v1/generations

Submit an authenticated generation job.

Readable text stays the invariant.

The API contract is available now. Workspace key issuance and asynchronous status endpoints are still in preview, so unauthenticated writes fail closed.

401

Predictable errors

Every failure includes a stable code, request ID, and optional structured details.

{
  "code": "UNAUTHORIZED",
  "request_id": "req_01J…"
}