CreativeClaw · Authentication Profile

CreativeClaw Authentication

Authentication

CreativeClaw secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyArtificial IntelligenceGenerative AIImage GenerationVideo GenerationAudioMCPMarketing

Methods: http, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

oauth2 oauth2

· flows: authorizationCode

bearerAuth http

scheme: bearer

Source

Authentication Profile

generated: '2026-11-04'
method: searched
source: https://creativeclaw.co/auth.md
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://clerk.creativeclaw.co/oauth/authorize
    tokenUrl: https://clerk.creativeclaw.co/oauth/token
    scopes: 2
  description: OAuth 2.1 authorization code with PKCE S256. Dynamic client registration is supported. Request only `profile`
    and `email`.
  sources:
  - openapi/creativeclaw-co-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: 'Access token from the Clerk token endpoint, sent as `Authorization: Bearer <token>`.'
  sources:
  - openapi/creativeclaw-co-openapi.yml
derived_from: openapi/creativeclaw-co-openapi.yml
docs: https://creativeclaw.co/auth.md
documented:
  discovery: Unauthenticated tools/call on POST /mcp returns HTTP 401 with a WWW-Authenticate Bearer challenge whose resource_metadata
    points at https://app.creativeclaw.co/.well-known/oauth-protected-resource/mcp (RFC 9728); authorization server metadata
    (RFC 8414) at https://app.creativeclaw.co/.well-known/oauth-authorization-server.
  pkce: S256 (required)
  dynamic_client_registration: https://clerk.creativeclaw.co/oauth/register (RFC 7591), public client
  authorization_endpoint: https://clerk.creativeclaw.co/oauth/authorize
  token_endpoint: https://clerk.creativeclaw.co/oauth/token
  revocation_endpoint: https://clerk.creativeclaw.co/oauth/token/revoke
  jwks: https://clerk.creativeclaw.co/.well-known/jwks.json
  identity_provider: Clerk (users typically sign in with Gmail)
  unauthenticated_methods:
  - initialize
  - notifications/initialized
  - ping
  not_offered:
  - agent_auth
  - identity_assertion
  - service_auth
  - id-jag
  - provider API keys
  note: Docs say "Never request `openid`" — Clerk rejects that scope for dynamically registered MCP clients.

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/creativeclaw-co-authentication"

All security posture

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.