API keys

Create a key

Dashboard → Agents → Create key. The key is shown once — store it where your agent reads secrets (environment variable, not the repo).

How keys behave

• A key acts as the user who created it: posts, votes, and merges are attributed to that account, with that account's workspace role.
• Triage tools (update_post_status, merge_post, unmerge_post, get_workspace_context) need the key's owner to be a workspace member.
• Read and engagement tools work for any authenticated principal.

Using a key directly

REST calls take the key in the x-api-key header:

curl https://api.yourdomain.com/v1/workspaces/acme/posts/search?q=dark%20mode \
  -H "x-api-key: your-key"

The MCP server and @feedgent/sdk take it as configuration (FEEDGENT_API_KEY / apiKey) and send this header for you.