zai-keys

You help an agent's human get a Z.ai GLM key that Claude Code can use through Immersive Commons. IC holds ONE Z.ai org key server-side and fans out per-member virtual keys metered through an IC gateway — you (the agent) never see the org key, only the minted per-member proxy key (agt_…). Two flavors:

• Workshop pass (anyone, even a brand-new public-tier member): a 5-hour time-boxed key tied to an upcoming IC event you're attending. The walk-in path for a Vibe Coding Night / ClawCamp / workshop.
• Member key (ic-member+): a weekly-token key at a multiplier (1 / 2 / 5 / 10 / 20× the base weekly allowance). Resets every Monday, never expires.

The shape is request → operator approves → key is minted. You file the request; an IC operator (Ray) approves before any key exists. You cannot mint your own key — that is the whole point of the gate.

Pre-flight (always)

• Token + scope. You need an agt_* IC agent token carrying keys:request. It's granted at every tier (public → operator), so any token can file a request. No token yet? Run ic-onboarding and include keys:request in the scope array.
• Smoke-check the token + scope:

  curl -s -H "Authorization: Bearer $FLOOR10_AGENT_TOKEN" \
    https://www.immersivecommons.com/api/mcp \
    -H "Content-Type: application/json" \
    -H "Accept: application/json, text/event-stream" \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ic_get_my_membership","arguments":{}}}'
  

  A token missing required scope: keys:request on the request tool below means your tier didn't grant it — re-mint with the scope (see ic-onboarding). The MCP Accept: application/json, text/event-stream header is mandatory; without it the server returns -32000 Not Acceptable.
• Pick the right key type with the human before filing. Don't request both. If they're at an event and just want to code for the session → workshop. If they want a standing weekly allowance → member (needs ic-member; below that the member tool errors and the fix is a tier upgrade, not a re-mint).