JOGL Network Docs

API keys

Mint keys, connect tools, and enable API writes for your community.

Settings → API keys is where you create API keys and connect external tools (including LLM agents) to JOGL Network. This page is the admin-facing companion to the developer Authentication reference.

Connect a tool

The Connect a tool panel gives you the MCP server endpoint (a branded one-click OAuth URL, or the raw Supabase functions URL with an API key), pre-filled for the correct environment, ready to copy into Claude Code, Claude Desktop, or another MCP client.

Create a key

Create keys with a scope tier:

  • Readsearch:read, profile:read, enrich:read.
  • Read + Write — adds member:write and enrich:write.

An Advanced expander exposes granular scopes, including the side-effecting self:enrich. Keys are personal (minted by you, for you) and the secret is shown once at creation. You can create keys in live or test environments.

Enabling write access

Read keys work immediately. Write keys additionally require you to turn on Write access for the owning account (your personal account, or each organization you own/administer):

  • Enabling records a versioned write attestation and flips the account's write flag on.
  • Enabling for a community's owner also lets that community's admins add members via the API.

There's also a write-consent queue for just-in-time approvals, and a Connected apps section for OAuth (WorkOS) connectors — each connector's write capability is gated by the same attestation.

Enabling write access authorizes automated changes to your communities' data. Only enable it for keys and connectors you trust, and revoke anything you're unsure about — revocation takes effect on the next request.

On this page