geldata.com
Gel exposes a `gel` CLI plus optional per-instance EdgeQL-over-HTTP and GraphQL endpoints; authentication is via CLI `gel cloud login`, Gel Cloud secret keys, or database credentials/JWTs on the HTTP surfaces.
- Gel EdgeQL over HTTPdiscovered
- Gel GraphQL endpointdiscovered
- Gel CLIdiscovered
Create a Gel Cloud secret key from the Gel Cloud CLI docs. The connection docs state that to authenticate with a Gel Cloud instance you provide the instance name and a secret key; the Cloud docs also say you can generate a secret key in the Cloud UI or by running gel cloud secretkey create.
$ gel cloud loginAcquired by the CLI — running gel cloud login opens the auth flow and stores the credential.
Create or set a database role password on your Gel instance. The docs note Gel creates an admin user by default with a randomized password, and you can set one with alter role admin { set password := '<password>'; }; or create a new role with create superuser role <name> { set password := '<password>'; };. For linked or local instances, the CLI can also save these credentials locally as described in Connection parameters.
Configure your Gel instance to use cfg::JWT for the SIMPLE_HTTP transport as described in EdgeQL over HTTP. Then mint a JWT for a Gel database user according to your instance's JWT configuration. Requests must include Authorization: Bearer <token> and X-EdgeDB-User: <gel-username>.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing