Developers / API
GEN API. In your services.
The entry point for connecting GEN to a service, from your infrastructure.
Request API accessContext and intentConceptual example
{ "intent": "prepare a summary", "context": ["selected notes"], "validation": "human" }Proposal to reviewConceptual example
{ "result": "Draft proposed", "status": "pending validation" }From your service to the response
Identify the expected action, the context needed and who will validate the result. The examples above illustrate an exchange and do not define an API schema.
Authentication and reference
Authentication methods, routes, quotas and errors will be documented when developer access opens.
Sovereignty, privacy by design and zero-knowledge
For a ONE integration, document where storage and processing take place, what access each connector requests and how to revoke it. Privacy by design starts by limiting data and rights to what is necessary. A zero-knowledge guarantee is assessed per component: it depends notably on key management and the service's access to data in the clear. It does not extend by default to all connected tools.