ChatGPT Plugin

Folded Page

A journal that grows with you.

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Keep a journal. See your story take shape. Journal with ChatGPT. Save a moment as it happened, or talk it through and keep the reflection you agree on. Folded Page stores your original words and agreed reflections separately. You decide what to save. Shape your private Story of you together: up to 200 words about the people, interests, and experiences that matter to you. You can start in your first conversation. Refine it when you find a better way to describe yourself, and approve the wording before ChatGPT saves a change. Earlier versions stay available to read or restore. Return to your journal in a new conversation. Ask what you wanted to try, or revisit an experience that feels relevant today. ChatGPT can look through summaries and return to your original entries to explore a connection with you. On foldedpage.app, read your Story and its history, inspect and correct your entries, download your journal, or disconnect ChatGPT. A Folded Page account is required.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-31
Tool count: 17
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Folded Page has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

17 tools agents can invoke

Add explicitly supplied material to an existing entry without replacing its earlier words. Requires current expected_revision. Distinct moments should normally be separate entries.
Save an intentional journal entry after the person asks or agrees to save. Preserve supplied words; reflection is separate and must be agreed. Reuse request_key only for identical retries. Returns durable entry ID and revision; use get to inspect.
Retrieve a current, nontrashed entry, with distinct contribution and reflection.
Read the person's approved Story of you and current revision, or inspect one historical revision. An absent story is a normal initial state. Source availability reflects current entry access; the story remains approved writing even if sources change or disappear.
Retrieve a bounded batch of ready summary tasks and the current view revision. Leaf tasks refer to entries: get the exact current entry before summarizing. Parent tasks include child summaries and immutable version IDs. Repeating this operation resumes bootstrap or interrupted upkeep; it does not claim work.
Read the portable journal view: at most 16 KB of stored summary nodes, plus version, coverage and pending-work status. Recent entries have more detail. Optional revision inspects history. Incomplete coverage is explicit; summaries are interpretations of sources, not new evidence.
List current journal entries by experience date, newest first. Pass next_cursor fields for the next page.
On the person's request, make a historical story current through a new version. Requires expected_revision and an identical-retry request_key. Missing related entries do not prevent restoration. Historical text records what the person approved then.
On the person's request, restore an earlier summary/tree state as a new version. Journal entries are preserved, including newer ones. Edited/deleted sources cannot be reactivated unchanged; incompatible summaries return to pending work. Requires current expected_revision and an identical-retry request_key.
Retrieve current journal matches using text and semantic search. Results are stored excerpts labeled by authorship, never generated analysis. Text fallback is explicit.
Read approved story versions and their writer, time and optional related entry references. Source availability reflects current deletion rules.
Move an entry into recoverable trash for 30 days. Requires current expected_revision. Permanent deletion and recovery are website operations.
Replace an entry with explicitly agreed corrections. Preserves immutable prior revisions. Requires current expected_revision; on revision_conflict, get current entry and reconsider. Never silently merge.
Page journal-view versions, their writer connection, times and change counts. Use get_view with a revision to inspect and zoom its exact sources. Historical summaries remain subject to current access/deletion rules.
Save exactly the approved replacement story, at most 200 whitespace-separated words, as a new immutable version. Host assistants write with the person's agreement; the server does not write prose. Optional sources are entry IDs and known revision numbers, with no cached source text. Requires expected_revision (0 initially); on conflict reread and reconsider approved text. Reuse request_key only for an identical retry. Entry and story saves are separate; report partial success accurately.
Store host-written leaf/parent summaries, at most 512 UTF-8 bytes each, after an authorized journal save or requested correction. Supply expected_revision, expected_node_version (null for unfinished tasks), and the exact entry_revision or left/right child versions. The server advances the tree/view without an LLM. On conflict, reread and reconsider; identical uncertain retries reuse request_key. Returns a content-free receipt, not the current view.
Open an immutable node version into its two children, or its exact source entry revision at a leaf. Preserves distinct contribution/reflection and dates. Current deletion rules apply to historical nodes too. Use source details before drawing a consequential connection.

FAQs

Folded Page ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Folded Page's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.