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/agentrux-com:agentrux-com-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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: AgenTrux Well Known API
  version: 0.1.0
tags:
- name: .well Known
paths:
  /.well-known/jwks.json:
    get:
      tags:
      - .well Known
      summary: Jwks
      operationId: jwks__well_known_jwks_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Jwks  Well Known Jwks Json Get
  /.well-known/echo_policy_capability:
    get:
      tags:
      - .well Known
      summary: Echo Policy Capability
      description: 'Echo Policy server-side capability advertisement.


        SSOT: docs/04_design/messaging/echo_policy.md §3-3

        SDK は client init 時に同期 probe して field_support / server_filter_support を確定。


        P2 で SSE hint frame + hint_summary catch-up + Hint dataclass に producer_script_id

        field を追加完了、 field_support=true に切替。'
      operationId: echo_policy_capability__well_known_echo_policy_capability_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Echo Policy Capability  Well Known Echo Policy Capability Get
  /.well-known/oauth-authorization-server:
    get:
      tags:
      - .well Known
      summary: Oauth Authorization Server
      description: 'RFC 8414 Authorization Server Metadata.


        SSOT: docs/05_api/endpoints_public.md §4-5'
      operationId: oauth_authorization_server__well_known_oauth_authorization_server_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Oauth Authorization Server  Well Known Oauth Authorization Server Get
  /.well-known/oauth-protected-resource/mcp:
    get:
      tags:
      - .well Known
      summary: Oauth Protected Resource Mcp
      description: 'RFC 9728 既定 `/mcp` 用 PRM (mcp_auth_level_v1.md §11、極小応答)。


        ディレクトリ掲載 (OpenAI / Anthropic) の固定 URL 導線は「固定 production URL に

        OAuth して使い始める」動線が前提で、per-connection URL (Console の事前払い出し)

        では成立しない。2026-07-23 に削除した discovery を **これ 1 本と /mcp の 401

        ヘッダに限って** 復活させる (接続の推奨は引き続き per-connection URL = §4-3)。


        応答は per-connection PRM と同一形状の極小応答: resource URI + AS ポインタ +

        vocab scopes のみ。Script 名 / alias / account / topic は載せない (§3-4 の極小化)。

        account 依存の情報が無いので DB も認証も不要 = 全リクエストで同一応答。'
      operationId: oauth_protected_resource_mcp__well_known_oauth_protected_resource_mcp_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/oauth-protected-resource/mcp/c/{slug}:
    get:
      tags:
      - .well Known
      summary: Oauth Protected Resource Mcp Connection
      description: 'RFC 9728 per-connection PRM (mcp_auth_level_v1.md §3-4、極小応答).


        - active slug = 200。応答は resource URI + AS ポインタ + vocab scopes のみ

        (Script 名 / alias / account 情報 / per-topic scope は載せない。全 slug で同一形状)

        - unknown / revoked = 404 (存在オラクル最小化、401/404 ポリシーは §3-4 #3)

        - 発見動線は /mcp/c/{slug} の 401 WWW-Authenticate resource_metadata (受動的)'
      operationId: oauth_protected_resource_mcp_connection__well_known_oauth_protected_resource_mcp_c__slug__get
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
          title: Slug
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /.well-known/agent-card.json:
    get:
      tags:
      - .well Known
      summary: Agent Card
      description: 'A2A Agent Card. SSOT: docs/05_api/endpoints_public.md §4-5.'
      operationId: agent_card__well_known_agent_card_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/agent.json:
    get:
      tags:
      - .well Known
      summary: Agent Card Legacy
      description: Legacy A2A path — 301 redirect to /.well-known/agent-card.json.
      operationId: agent_card_legacy__well_known_agent_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/mcp/server-card.json:
    get:
      tags:
      - .well Known
      summary: Mcp Server Card
      description: 'MCP static server card (SEP-1649 提案準拠)。SSOT: endpoints_public.md §4-5.


        ディレクトリ (Smithery 等) は掲載時にサーバーを自動スキャンして tool 一覧を取る。

        AgenTrux の /mcp は OAuth 必須 (401) なのでスキャンは auth wall で失敗する。

        本 card を無認証で配ることでスキャンを不要にする。


        内容は **公開契約 mcp_contract が唯一の出所** で、`initialize` の serverInfo と

        `tools/list` の tools と同一値になる (2 箇所に書かないことでドリフトを防ぐ。

        テスト: tests/integration/test_mcp_server_card.py が実 MCP 応答と突合)。

        `resources` / `prompts` は接続の Grant 次第で内容が変わる (静的に列挙できない) ため

        省略する — spec 上 optional (Codex plan review 2026-09-11 #1)。'
      operationId: mcp_server_card__well_known_mcp_server_card_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError