journalize-dev .well Known API

The .well Known API from journalize-dev — 2 operation(s) for .well known.

Operations 2

GET /.well-known/402index-verify.txt Index402 Verify #
GET /.well-known/security.txt Security Txt #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/journalize-dev:journalize-dev-well-known-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

journalize-dev-well-known-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: journalize .well Known API
  contact:
    name: Journalize
    email: hello@journalize.dev
  version: 0.1.0
tags:
- name: .well Known
paths:
  /.well-known/402index-verify.txt:
    get:
      summary: Index402 Verify
      description: 'Domain-ownership proof for 402index.io''s directory listing (see

        https://402index.io/verify) — must contain ONLY the verification hash

        they issued, no extra whitespace or content. Read from disk rather

        than inlined here so a future re-claim/rotation is a file swap, not a

        code change, matching the security.txt/robots.txt pattern above.'
      operationId: index402_verify__well_known_402index_verify_txt_get
      responses:
        '200':
          description: Successful Response
          content:
            text/plain:
              schema:
                type: string
      tags:
      - .well Known
  /.well-known/security.txt:
    get:
      summary: Security Txt
      description: 'RFC 9116 canonical location — the only one search/security tooling

        actually checks by spec. The bare /security.txt route below exists

        only for older crawlers that predate the .well-known convention.'
      operationId: security_txt__well_known_security_txt_get
      responses:
        '200':
          description: Successful Response
          content:
            text/plain:
              schema:
                type: string
      tags:
      - .well Known