Peaka · Authentication Profile

Peaka Authentication

Authentication

Peaka supports two authentication mechanisms: OAuth for remote installs and API keys for local installs.

Peaka declares 2 security scheme(s) across its OpenAPI definitions.

CompanyData IntegrationAI-ReadyGovernanceAnalytics

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

Remote OAuth oauth2

PEAKA_API_KEY apiKey

Source

Authentication Profile

generated: '2026-10-21'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://www.peaka.com/docs/cookbook/how-to-create-peaka-rest-api-catalog-with-authentication/how-to-create-peaka-rest-api-catalog-with-authentication.md
sources:
- https://www.peaka.com/docs/cookbook/how-to-create-peaka-rest-api-catalog-with-authentication/how-to-create-peaka-rest-api-catalog-with-authentication.md
- https://www.peaka.com/docs/cookbook/how-to-generate-api-keys/how-to-generate-api-keys.md
- https://www.peaka.com/docs/cookbook/how-to-manage-partner-api-key/how-to-manage-partner-api-key.md
- https://www.peaka.com/docs/mcp/authentication/authentication.md
description: 'Peaka supports two authentication mechanisms: OAuth for remote installs and API keys for local installs.'
schemes:
- type: oauth2
  name: Remote OAuth
  evidence: When a client connects to `https://mcp.peaka.studio/mcp`, the server returns `401 Unauthorized` with OAuth metadata in the `WWW-Authenticate`
    header. Your MCP client opens a browser to `mcp.peaka.studio`, you sign in to Peaka, approve the consent screen, and the client receives an
    access token.
  how_to_obtain: User signs in via browser to `mcp.peaka.studio` and approves consent; the client receives an access token.
- type: apiKey
  name: PEAKA_API_KEY
  evidence: The NPM and from-source installs read a Peaka API key from the `PEAKA_API_KEY` environment variable.
  location: env
  how_to_obtain: Generate an API key via the Peaka settings page (see “How to generate API Keys”) and provide it in the `PEAKA_API_KEY` environment
    variable.
docs: https://www.peaka.com/docs/cookbook/how-to-create-peaka-rest-api-catalog-with-authentication/how-to-create-peaka-rest-api-catalog-with-authentication.md

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/peaka-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.