API Blueprint · Authentication Profile

Api Blueprint Authentication

Authentication

API Blueprint declares 0 security scheme(s) across its OpenAPI definitions.

API DesignSpecification LanguageMarkdownDocumentationAPI Description LanguageParsingOpen SourceDeveloper Tools
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑
generated: '2026-09-02'
method: probed
source: >-
  derive-authentication.py produced nothing because the provider's contract
  declares no securitySchemes — correctly, because the API has no
  authentication at all. This file records that as a positive finding rather
  than an absence. Established by unauthenticated live probes of
  https://api.apiblueprint.org on 2026-09-02 and by reading the provider's API
  Blueprint contract in apib/, which documents no credential of any kind.
provider: API Blueprint
providerId: api-blueprint
summary: >-
  The API Blueprint parsing service is completely open. There is no API key, no
  token, no OAuth flow, no sign-up and no account. Every operation was called
  successfully on 2026-09-02 with no credential.
schemes: []
authentication_required: false
signup_required: false
schemes_detail:
  - id: none
    type: none
    description: >-
      No authentication. Confirmed by calling every operation anonymously:
      GET / -> 200; POST /parser with an API Blueprint body -> 200 with a parse
      result; POST /validate -> 200; POST /transform -> 200. No 401 or 403 was
      returned by any request during the pass.
discovery:
  - path: /.well-known/oauth-authorization-server
    host: api.apiblueprint.org
    status: 404
  - path: /.well-known/openid-configuration
    host: api.apiblueprint.org
    status: 404
  - path: /.well-known/oauth-protected-resource
    host: api.apiblueprint.org
    status: 404
  - path: /.well-known/oauth-authorization-server
    host: apiblueprint.org
    status: 404
  - path: /.well-known/openid-configuration
    host: apiblueprint.org
    status: 404
transport:
  https: true
  tls_version: TLSv1.2
  hsts: false
  note: >-
    TLS observed at TLSv1.2 on api.apiblueprint.org (the marketing host
    apiblueprint.org negotiates TLSv1.3). HSTS is not set on either host. See
    security/api-blueprint-domain-security.yml.
agent_note: >-
  An agent can call this API with no onboarding step whatsoever. That is the
  strongest agent-access property in this profile and the weakest security one:
  there is no way to attribute, meter or revoke a caller, and no rate limit is
  published or observed.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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/api-blueprint-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.

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