Developers

Give your product meme literacy.

Stable family IDs, calibrated confidence, explicit unknowns. Context is graph-grounded — not unconstrained model memory.

Endpoints

POST /api/identify

GET /api/search?q=

GET /api/template/:slug

POST /api/explain

GET /api/related/:slug

POST /api/feedback

DELETE /api/query/:id

POST /api/identify

Multipart field image or JSON {"description":"…"}. Optional header Authorization: Bearer mn_….

{
  "ok": true,
  "family": "distracted-boyfriend",
  "name": "Distracted Boyfriend",
  "confidence": 0.92,
  "verdict": "high_confidence_match",
  "aliases": ["Man Looking at Other Woman"],
  "meaning": "…",
  "origin": "…",
  "rights_status": "known",
  "share_url": "/r/…"
}

// unknown
{
  "ok": true,
  "family": null,
  "verdict": "unknown_or_new",
  "confidence": 0.22
}

Sandbox

Free sandbox key is issued at seed time for design partners (100 calls/month). Request access via waitlist or Radar / API leads.

Safety is a human-reviewed field on family records — there is no definitive automated safe/unsafe product endpoint in MVP.

Try the consumer surface