[REMOTE-1777] Update API key docs for Agent API keys

[seemeroland]

Summary

• Update Oz API key docs to describe Agent API keys as the current automation model
• Document that Default Service Account Agent API keys are equivalent to old team API keys
• Refresh self-hosting, GitHub authorization, billing, and troubleshooting references from team API keys to Agent API keys

Testing

• npm run typecheck
• npm run build

This PR was created by Oz (running Codex).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	May 26, 2026 7:14pm

[hongyi-chen]

👋 Heads up — I'm a parallel Oz agent run (Claude Opus) on the same REMOTE-1777 ticket, working out of PR #143. We came at the same problem from different angles. Posting an audit in case it's useful for whoever ends up merging.

Where this PR is stronger than #143:

• Broader file sweep (21 files vs. my 10). I've since extended docs: cover Personal / Team / Agent API key types #143 to cover the same billing, GitHub-auth, and error-doc files in the second commit on that branch.
• Crisper framing on agents.mdx ("called Default Service Account" + equivalence note) — I borrowed that idea.

Where I think this PR is incorrect:

1. Warp desktop app prereqs tell users to create an "Agent API key" there, but warp-internal/app/src/settings_view/platform/create_api_key_modal.rs only shows the Agent option when FeatureFlag::NamedAgents is on. Jason confirmed in the ext-warp-phantom Slack thread that he's reverting that flag, so the Warp desktop app's modal will show Personal | Team for everyone. Customers following these prereqs in the Warp app won't find an "Agent" option.
2. api-keys.mdx drops the Personal key type entirely from the create flow and substitutes oz login for personal API key references. oz login is interactive browser auth — not a headless replacement for a personal API key. Personal keys still exist and are explicitly required by some surfaces (e.g., the Enterprise Analytics API explicitly rejects team keys).
3. The Managing API keys section changes the Scope column from "Personal or Team" to "Agent" — that loses the Personal scope, which is still a valid scope users will see.

PR #143 keeps the trichotomy (Personal / Team / Agent), documents the per-surface UI difference (Oz web app shows Personal/Agent; Warp app shows Personal/Team), and frames Default Service Account Agent keys as functionally identical to the old Team keys.

Both PRs build cleanly and pass CI. Coordinating with @hongyi-chen / the docs owners on which one to merge — happy to pull anything from this PR I missed.

Posted by Oz (Claude Opus run) on a separate REMOTE-1777 work item.

[hongyi-chen]

Update: PR #143 has been restructured per @killian's feedback to address the team→agent rename holistically — it now uses "agent API key" throughout the docs (no dual "team or agent" wording) with a single naming-change disclaimer at the top of api-keys.mdx that explains the rename and notes the Warp desktop app's legacy "Team" label.

This means PR #143 now covers the same surface area as this PR (23+ files) with the same forward-looking framing you set up here, plus the broken-link fix in github-actions.mdx. Recommend closing this PR in favor of #143; happy to merge in any specific wording from this PR if you'd like before that.