Knostic · Authentication Profile

Knostic Authentication

Authentication

Knostic secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanySecurityArtificial IntelligenceAI AgentsAgent SecuritySupply Chain SecurityMCPThreat IntelligenceDeveloper ToolsShadow AI
Methods: http Schemes: 1 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer · in: header (Authorization)

Source

Authentication Profile

Raw ↑
generated: '2026-07-19'
method: searched
source: https://agentmesh.knostic.ai/api
docs: https://agentmesh.knostic.ai/api
summary:
  types:
  - http
  api_key_in:
  - header
  oauth2_flows: []
  notes: >-
    AgentMesh authenticates API callers with a bearer API key minted from the AgentMesh
    console. There is no OAuth 2.0 / OpenID Connect surface on the public API, so no
    scopes artifact is emitted. Console (browser) sessions are brokered by Descope as
    the identity provider, but that is the console's own login, not the API contract.
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  in: header
  parameter: Authorization
  format: 'Authorization: Bearer <api_key>'
  description: >-
    AgentMesh API key. Created from the console via POST /api/console/keys and sent on
    every request as an Authorization bearer token.
  sources:
  - openapi/knostic-agentmesh-openapi.yml
tiers:
- tier: anonymous
  description: >-
    Read endpoints (/skills, /mcp, /extensions) answer unauthenticated requests at a
    reduced tier. Verified live 2026-07-19: responses carry the header `X-Tier: anonymous`.
  requires_key: false
  endpoints:
  - GET /skills
  - GET /mcp
  - GET /extensions
- tier: api-key
  description: >-
    Scan endpoints require a valid API key; each key carries its own daily scan quota and
    can only read back the scans it created.
  requires_key: true
  endpoints:
  - POST /scan/skill/{slug}
  - POST /scan/extension/{slug}
  - GET /scans
  - GET /scans/{scan_id}
key_management:
  console: https://agentmesh.knostic.ai/console
  create_key_endpoint: POST /api/console/keys
  identity_provider: Descope
  notes: >-
    Console endpoints (/api/console/me, /api/console/keys, /api/console/artefacts) are
    session-scoped browser APIs behind the Descope login; they additionally send an
    X-User-Email header. They are not part of the public API contract.
failure_modes:
- status: 401
  detail: Missing or invalid API key
- status: 403
  detail: Scan belongs to a different API key

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/knostic-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 email required.

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