Notes on how we designed API keys in GPTpost, in case it is useful to others building agent access.

  • Scopes: accounts:read, posts:read, posts:write, media:write
  • Ceiling: a key never exceeds its creator’s current rights
  • Lifecycle: creator loses role or is removed, key stops working; password change, reset or 2FA replacement revokes their keys
  • Storage: shown once, stored hashed
  • Same rules: text limits, approvals, plan limits apply to agent posts too

The ceiling rule was the important one for us. Without it, a key created by an admin who later gets demoted becomes a privilege that outlives the role.

Docs: https://oraglegpt.org/use-cases/social-media-api/

What else would you want before letting an agent post for your org: per-key IP allowlists, audit logs, something else?

https://oraglegpt.org/use-cases/social-media-api/