Knowledge
Create and revise documents, manage spaces and page trees, add comments, labels, backlinks, watchers, and permissions.
An API under the workspace
Knowledge that moves to the work.
Findset exposes a versioned API for pages, spaces, files, search, permissions, and product usage. Signed StackDeck services can contribute files and retrieve approved context inside workspace boundaries.
- Versioned API
- Signed service requests
- Workspace-scoped data
The API that exists today
Every part of StackDeck uses the same knowledge primitives.
The current API is available to authenticated Findset sessions and registered StackDeck services. API keys for outside developers are next.
Files
Initiate and finalize uploads, inspect versions, create signed downloads, manage lifecycle, and export workspace data.
Discovery
Search files, native document content, and records from across StackDeck within the active workspace.
Product services
Accept signed uploads, pin exact file versions to product usage, and issue revocable public renditions for clean assets.
Built into StackDeck
Find every product's records in Findset.
Findset indexes enough metadata to make a record discoverable and returns the user to the place in StackDeck that can act on it.
Frontroom
Discover published pages and keep their approved files pinned to the exact clean version Frontroom uses.
PostDesk
Find templates and campaigns, then return to PostDesk for editing, consent checks, and sending operations.
Ziplet
Find short links and open Ziplet for destinations, QR codes, and link reporting.
External developer access
A public developer platform is next.
External API keys, OAuth applications, webhooks, rate-limit contracts, and public reference documentation are product direction. They build on today's versioned API and signed-service model.
Signed StackDeck service API
Current: authenticated user sessions and scoped Core-issued service tokens, with request IDs for service writes.
Public developer platform
Direction: scoped developer credentials, webhook subscriptions, stable SDKs, and documentation for approved workspace integrations.
Public delivery, private storage
Share one approved file, keep the rest private.
Public renditions are created from clean versions and resolve through revocable tokens. The underlying object remains in private clean storage.
01
Choose an approved version
The service names a ready file version that already passed the upload pipeline.02
Create a tokenized rendition
Findset stores only a hash of the random public token and links it to that exact version.03
Revoke in one step
Revoking the rendition closes public lookup while the workspace file and its history remain intact.
Where Replydeck fits
Next: Replydeck answers from approved knowledge.
The intended model is for Replydeck to query Findset for workspace-approved answers and source context. That keeps the wiki, the agent answer, and future public help content on one knowledge lineage.
Build on one knowledge layer
Keep one copy of every answer.
Use Findset as the workspace-owned knowledge source and keep operational records in the products responsible for them.