
Ask and Retrieve for a person who connected your company. Improve your product for them. This is not a public user pool and not a purchase of their data.
Purpose, scope, user control, then a receipt. Commercial terms come after we review your use case.
1
They authorize your company to use their memory so you can personalize your product for them. That is not a data sale.
POST /api/marketplace/ask-query
POST /api/marketplace/retrieve-query2
A query you run is the same connected-access product as a query they run in an app they use: memory they authorized, used to personalize the product for them.
3
They choose what you can use and can revoke it.
4
Users can inspect what was shared and revoke going forward.
Same memory graph. Two ways to query one connected user.
Synthesized context for someone who connected you.
POST /api/marketplace/ask-querytarget_user_id, query
since, as_of, focus (optional)
include_evidence (requires Detailed on at least one origin)
1
Start from a customer already in your systems, after they connected your company.
2
They choose source groups. Sensitive is a separate company-sheet toggle.
3
Returns context and optional quoted snippets — not identity fields, open URLs, or live mailbox fetches.
Structured graph for someone who connected you.
POST /api/marketplace/retrieve-querytarget_user_id, query or entity or entity_id
since, as_of, origins, limit, threshold (optional)
include_evidence (requires Detailed on at least one origin)
1
Same company grant as Ask.
2
Returns anonymized profile, scored entities, facts, and edges.
3
Evidence adds quoted snippets — not full artifacts, open URLs, or identity fields.
Every assistant is building a private profile of its users. That profile is stuck where it was made — ChatGPT memory does not follow someone to Claude, Cursor, or your product. Cognitia is the user-owned graph they can inspect, and the consent surface they use to let your product use a slice.