Skip to main content
Your product keeps its users, tenants, data, and pages. Opengeni runs the agent sessions. They meet at one backend route and at the tools you expose.
  1. The browser talks to your own origin at /api/opengeni.
  2. Your proxy checks your session and forwards the request to Opengeni as that user.
  3. Opengeni runs the agent, which calls your API through the tools you gave it.
The API key stays on your server.

Mapping your product onto Opengeni

What your proxy’s resolve returns picks the workspace: one per tenant, one per user, or one you name. See Users, tenants & privacy.

Who does what

Using a coding agent? The opengeni-client skill covers this.