Repository navigation
Conversation
Add a how-to page on API keys: create one on the account page, send it as a bearer token or X-API-Key header, where it applies (API and MCP, not Studio), per-account limits, and the 401 and 429 errors. Say in the home page that keys are optional and link the new page from the MCP connection paragraph and the account question. Add the page to the Build nav. Part of DevelopmentFinanceObservatory/website#142. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015QQk2mKJZzXv2AYykDjvQf
This was referenced Nov 16, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The website's platform proxy now accepts optional API keys (website#143, part of website#142). This adds a how-to page for them and says on the home page that keys are optional. Anonymous access is unchanged, and the page says so.
The page covers:
/account/api-keys(shown once, up to 5 per account, delete to revoke, about a minute to take effect).Authorization: Bearer <key>orX-API-Key: <key>, never in the query string, and the 400 when both headers differ./api/v1/*,/openapi.json,/codes,/mcp; not Studio).invalid_api_key(no fallback to anonymous) and 429rate_limitedwithRetry-AfterandX-RateLimit-*.Pages changed
content/hub/build/api-keys.md: new page, "Use an API key", under Build with the DFO.hub.yaml: nav entry for the new page.content/hub/index.md: the MCP connection paragraph and "Do I need an account?" now say keys are optional and link the new page.Not in this PR
The API quickstart ("The API accepts requests without an API key.") and the MCP connect page ("No token is needed.", the HTTP 429 row) live in the
apisandairepositories (docs/guide/), which this build fetches. They need their own small PRs to say keys are optional and to link/docs/build/api-keys. This page links to both.How verified
uv run ruff check .,uv run ruff format --check .,uv run pytest(819 passed).uv run python scripts/build.pysucceeds and the page is in the corpus and manifest.lychee --config lychee.tomlover the built corpus: 0 errors./api/v1/graph/capabilities. The 429 example is from the website's local test run. A keyed call has not been run against production, because the feature is not deployed yet.Coordination
Publish after website#143 is deployed, so the page does not describe a key page that does not exist yet. Part of DevelopmentFinanceObservatory/website#142.
Claude-generated draft.
🤖 Generated with Claude Code
https://claude.ai/code/session_015QQk2mKJZzXv2AYykDjvQf