DreamGraph V1.1 · REST + MCP

Dream interpretation API for context-aware dream analysis.

Add reflective dream interpretation or structured dream parsing to an app, journal, sleep product, publication, research tool, or AI agent—without reducing every symbol to one fixed meaning.

2 no-key surfaces2 MCP tools6K characters/requestV1.1 versioned contract
01

Context changes meaning

“Snake” is not the answer. Calmly watching one and fleeing one are different inputs.

02

Reason trace included

Consumers can see which structured factors shaped the reflection instead of receiving an unexplained verdict.

03

Claims stay typed

Reviewed claims carry provenance. Personal inference stays separate from empirical or cultural claims.

04

Built to distribute

Origin-scoped partners, server-side keys, quotas, request IDs, CORS rules, attribution, and an embed path are already wired.

00

Free dream parsing API—no key required

A real public endpoint for prototypes, classrooms, evaluations, and low-volume tools. It parses structure; it does not generate a reading.

POST · public · CORS *
curl https://mydreamthreads.xyz/api/v1/dreamgraph/public/parse \
  -H "Content-Type: application/json" \
  -d '{
    "text": "I watched a snake in my garden. I felt peaceful."
  }'
12/min per client100/day per clientNo storage of dream textNo contribution created

Returns structured entities, actors, locations, actions, emotions, agency, threat, outcome, sensory cues, and recurrence. For a contextual reflection, use the authenticated /interpret endpoint.

00A

Public dream MCP server for AI agents

Connect any compatible Model Context Protocol client over Streamable HTTP. No API key is required.

STREAMABLE HTTP · PUBLIC
{
  "servers": {
    "dreamthreads": {
      "type": "http",
      "url": "https://mydreamthreads.xyz/mcp"
    }
  }
}
parse_dream structured extractionsearch_dream_concepts DreamGraph vocabularyNo storage of dream text60/min protocol requests

Endpoint: https://mydreamthreads.xyz/mcp · Complete dream MCP server guide · MCP server manifest. Results carry DreamThreads attribution and explicit boundaries against diagnosis, prediction, supernatural claims, and fixed symbolic meaning.

01

Quickstart

One POST from your server. The key is issued once and belongs in your secret manager.

curl https://mydreamthreads.xyz/api/v1/dreamgraph/interpret \
  -H "Authorization: Bearer $DREAMTHREADS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Request-ID: your-request-123" \
  -d '{
    "text": "I watched a snake in my garden. I felt peaceful.",
    "waking_context": "I recently started caring for a garden."
  }'
02

Endpoints

GET/api/v1/dreamgraph/health

Free liveness check for integration tests and connectivity diagnostics.

No authentication
POST/api/v1/dreamgraph/public/parse

Free structured parsing without an API key. Dream text is processed in memory and is not stored or contributed.

Use for prototypes and evaluation · 12/min · 100/day
POST/api/v1/dreamgraph/interpret

Contextual reflection, structured dream, factor trace, provenance, diagnostics, timing, and attribution.

Use for user-facing analysis
POST/api/v1/dreamgraph/parse

Entities, actions, emotions, locations, agency, threat, outcome, recurrence, and parser version—without model-generated interpretation.

Use for tagging, routing, or your own UI

Download the complete OpenAPI 3.1 contract · Successes use { data, request_id, version }; errors use RFC 9457 Problem Details while preserving { error, request_id, version }.

03

Example response

This abbreviated example shows the contract. Production responses also include the structured dream, diagnostics, timing, engine and parser versions.

200 · application/json
{
  "data": {
    "interpretation": {
      "essence": "The dream may be holding change and attention together without treating either as a threat.",
      "symbols": [{
        "symbol": "snake",
        "note": "Your calm response weakens a simple danger reading."
      }],
      "reading": "The garden places the image inside something you actively tend. The dream may be exploring a change that asks for attention without requiring panic.",
      "question": "What change are you willing to observe before deciding what it means?",
      "reasonTrace": [
        { "factor": "emotion", "value": "peaceful" },
        { "factor": "action", "value": "observed" }
      ],
      "provenance": []
    },
    "attribution": {
      "provider": "DreamThreads",
      "deep_link": "https://mydreamthreads.xyz/?utm_medium=api…"
    }
  },
  "request_id": "your-request-123",
  "version": "v1"
}
04

What to build

Journals

Context-aware reflections

Add a reading beside a private dream entry while keeping your product’s own journal experience.

Sleep products

Dream recall companion

Turn optional dream reports into structured themes without presenting a diagnosis or sleep score.

Publishers

Interactive dream utility

Embed an attributed interpreter inside relevant editorial pages and measure starts, completions, and referrals.

AI agents

A bounded dream tool

Give an agent a versioned endpoint with explicit safety language, structured factors, and provenance.

Researchers

Reproducible parsing

Use the parse endpoint for consistent fields. Population access is separate and minimum-N guarded.

Communities

Reflective prompts

Generate an open question and tentative possibilities without treating a symbol as a universal code.

05

REST API or embed?

REST API

Own the interface

Your server sends the dream and renders the JSON response. Best when you control the complete product experience.

  • Long-lived key stays server-side
  • Origin-scoped partner account
  • Interpret and parse endpoints
  • Returned attribution deep link
Hosted embed

Ship one script

DreamThreads hosts the responsive UI. Your approved domain receives a short-lived, origin-bound token.

  • No partner key in browser code
  • Visible DreamThreads attribution
  • Completion and referral measurement
  • Fastest publication integration
06

Dream interpretation API, analysis API, or dictionary API?

These phrases are often used interchangeably. The output contract is what actually matters.

Dream interpretation API

Contextual reflection

Returns a tentative reading in JSON and explains which emotions, actions, outcomes, recurrence, and waking context shaped it.

DreamThreads: yes
Dream analysis API

Structured factors + reasoning

Often another name for an interpretation API. DreamThreads makes the analysis inspectable through parsed fields, a factor trace, and typed provenance.

DreamThreads: yes
Dream dictionary API

Symbol lookup

Maps a symbol to a fixed definition. DreamThreads does not expose a universal symbol dictionary because the same image can change with context.

DreamThreads: intentionally no
07

Privacy, safety, reliability

Data boundary

No API dream enters the contribution corpus

Partner calls create operational run records, not population contributions. Do not send dream content without the disclosure and consent your product requires.

Interpretation boundary

Reflection, never diagnosis or prediction

Integrations must keep output tentative and must not market DreamThreads as medical, psychological, supernatural, or predictive certainty.

Operational boundary

Scoped credentials and observable failures

Keys are hashed at rest, tied to a partner, restricted by origin, rate-limited, pausable, and rotatable. Every response carries a request ID and contract version.

08

Dream interpretation API FAQ

What is a dream interpretation API?

A dream interpretation API lets an app send dream text to a server and receive structured analysis or a reflective interpretation as JSON. DreamThreads also returns parsed context, a factor trace, provenance when reviewed claims are used, and an attributed deep link.

How is this different from a dream dictionary API?

A symbol dictionary usually maps one word to one fixed meaning. DreamThreads weighs the dreamer's emotion, agency, action, threat, outcome, recurrence, waking context, and physiological context. The same snake can therefore produce different tentative readings in a peaceful garden and a frightening chase.

Is there a free dream interpretation API?

DreamThreads provides a free, no-key structured dream parser for prototypes and evaluation. It returns entities, actions, emotions, locations, agency, threat, outcome, and recurrence—but not a generated interpretation. Context-aware interpretation access remains review-based because it uses a protected model pipeline. The public parser is limited to 12 requests per minute and 100 per day per client.

Does DreamThreads have a public MCP server for AI agents?

Yes. Connect a Model Context Protocol client to https://mydreamthreads.xyz/mcp using Streamable HTTP. The no-key server exposes parse_dream for privacy-bounded structured extraction and search_dream_concepts for DreamGraph vocabulary. It does not store dream text or generate diagnoses, predictions, supernatural claims, or fixed symbolic meanings.

Can I call the API from browser JavaScript?

Do not expose a long-lived partner key in a browser. Call the REST API from your server, or use the DreamThreads embed, which exchanges a short-lived origin-bound token and keeps credentials out of client code.

Does the API diagnose or predict anything?

No. Outputs are reflective and tentative. They are not medical or mental-health diagnoses, predictions, or fixed meanings, and integrations must preserve that framing.

Does DreamThreads train on API dream text?

The partner API does not add dream text to the DreamGraph contribution corpus. Any structured population contribution is a separate first-party consent flow. Partners should disclose their own handling and obtain any consent their use case requires.

What does the API return?

The interpretation endpoint returns an essence, contextual symbol notes, a short reading, an open question, structured dream factors, a reason trace, provenance, diagnostics, timing, request ID, version, and DreamThreads attribution. The parse endpoint returns the structured dream without generating a reading.

Partner intake

Put DreamThreads inside something people already use.

Tell us what you are building. Approved pilots receive a scoped partner key or embed configuration, an origin allowlist, quota, integration review, and attribution path.

Human review · no automatic keys