Niche .well Known API

The .well Known API from Niche — 6 operation(s) for .well known.

GitHub OpenAPI

Operations 6

GET /.well-known/mcp.json Well Known Mcp #
GET /.well-known/agent-skills/index.json Agent Skills Manifest #
GET /.well-known/api-catalog Api Catalog #
GET /.well-known/glama.json Glama Connector Claim #
GET /.well-known/oauth-authorization-server Oauth Authorization Server #
GET /.well-known/oauth-protected-resource Oauth Protected Resource #

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/nicheangle-com:nicheangle-com-well-known-api"
All apis
curl "https://apis.io/api/v1/apis?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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

nicheangle-com-well-known-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Signal .well Known API
  version: 0.1.0
tags:
- name: .well Known
paths:
  /.well-known/mcp.json:
    get:
      summary: Well Known Mcp
      description: 'RFC-style discovery doc for the MCP server. Mirrors the OAuth

        discovery pattern — agents probe `/.well-known/mcp.json` to find the

        server URL + auth scheme without needing a pre-known path.


        Two access paths:

        1. Web tier (nicheangle.com/.well-known/mcp.json) — handled by the

        Next.js `/api/mcp-discovery` route at web/src/app/api/...

        Returns `{web_origin}/api/mcp` (Vercel rewrites to Fly internally).

        2. Direct API (niche-api.fly.dev/.well-known/mcp.json) — this

        handler. Returns the bare API endpoint `{api_origin}/mcp` (no

        `/api/` prefix; that''s a web-tier rewrite path). The

        human-facing surfaces (token issue, docs) point at the

        configured FRONTEND_URL so agents that arrived via the API host

        still get correct links into the user dashboard.'
      operationId: well_known_mcp__well_known_mcp_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/agent-skills/index.json:
    get:
      tags:
      - .well Known
      summary: Agent Skills Manifest
      description: 'Live agent-skills manifest. Generated from `mcp_tools.TOOLS` on

        every request so the manifest and `tools/list` can never drift.


        Shape (loose convention — there isn''t a formal standard yet; we use

        fields common to HeyNews, Glama, mcpservers.org listings):


        {

        "name": "Niche",

        "description": "...",

        "category": "...",

        "homepage": "...",

        "transports": ["streamable-http"],

        "endpoint": "https://api.nicheangle.com/mcp",

        "auth_methods": [...],

        "skill_count": 24, # example only — the live value is len(skills)

        "skills": [{name, description, tags}]

        }'
      operationId: agent_skills_manifest__well_known_agent_skills_index_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/api-catalog:
    get:
      tags:
      - .well Known
      summary: Api Catalog
      description: 'RFC 9727 api-catalog. Linkset JSON pointing at every machine-

        readable surface we expose: OpenAPI doc, MCP endpoint, agent-skills

        manifest, docs site. The canonical entry point for API discovery

        crawlers and tooling that doesn''t know about Niche specifically.'
      operationId: api_catalog__well_known_api_catalog_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/glama.json:
    get:
      tags:
      - .well Known
      summary: Glama Connector Claim
      description: 'Glama connector ownership claim (glama.ai). Glama fetches this from the

        connector''s domain and verifies the `maintainers` email matches the Glama

        account email, then marks the listing as claimed. The email is env-driven

        (`GLAMA_MAINTAINER_EMAIL`), never hardcoded — no contact data in the repo,

        and it''s a public surface so it should be a COMPANY address. Unset → 404

        (unclaimed).'
      operationId: glama_connector_claim__well_known_glama_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/oauth-authorization-server:
    get:
      tags:
      - .well Known
      summary: Oauth Authorization Server
      description: 'RFC 8414 — authorization server metadata. Claude Desktop and

        ChatGPT app directory clients read this when an MCP server requires

        OAuth, to find the authorize / token / register endpoints + the

        supported flows.'
      operationId: oauth_authorization_server__well_known_oauth_authorization_server_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/oauth-protected-resource:
    get:
      tags:
      - .well Known
      summary: Oauth Protected Resource
      description: 'RFC 9728 — protected resource metadata. Tells the client which

        authorization servers can issue tokens for this MCP endpoint.'
      operationId: oauth_protected_resource__well_known_oauth_protected_resource_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}