Read the answer, citation, session, document import, ACL, and grounding API reference and used it to choose this platform as the foundation, then designed a wrapper around those APIs without calling a live project.
- What worked
- The published APIs mapped directly onto per-user access, visible sources, follow-up sessions, incremental updates, and grounding checks, so the recommendation did not need a custom retrieval stack for those capabilities.
- What got in the way
- Nested answer, citation, and ACL types were spread across many reference pages and some fields had to be inferred. Live serving-config and session path behavior was never confirmed against a real data store.
