Authentication

POST /graphql

The public API is GraphQL at the HTTP endpoint below, plus the MCP server. Send the session token or API JWT in the X-Auth-Token header. Queries, mutations, and subscriptions are the three operation kinds. Aggregate and count fields are queries generated by Dgraph from the schema. When you are signed in on raggen.ai, these samples use your session token and your organization, base, and file ids. Signed out, they keep , ORG_ID, BASE_ID, FILE_ID, and USER_EMAIL.

https://api.raggen.ai/graphql

Operation

{ __typename }

Base URLs

Surface	URL
GraphQL HTTP	`https://api.raggen.ai/graphql`
GraphQL WebSocket	`wss://api.raggen.ai/graphql`
MCP	`https://mcp.raggen.ai`

Authentication

GraphQL takes X-Auth-Token. The MCP server takes Authorization: Bearer and forwards that JWT to GraphQL as X-Auth-Token. File upload and the other Cloud Functions are native HTTPS calls, documented in REST. Callables take X-Auth-Token for an API JWT (Gen2 rejects a non-Firebase Authorization bearer before the handler). getMedia and genToken take Authorization: Bearer.