Cookie Settings

    We use cookies to improve your experience and optimize our service.

    Customize settings

    Essential

    Always active

    These cookies are required for the basic functionality of the website.

    Analytics & Performance

    These cookies help us understand how you use our website to improve it.

    For more information, see our Privacy Policy

    Skip to main content

    Public technical surface

    Aprixity Developer Resources

    Agents and developers can use this index to find supported read access, its contracts, and the boundary to protected services.

    Machine-readable contract

    OpenAPI 3.1.1 describes exactly the supported public read operations. These operations require no authentication.

    /openapi.json

    Public read operations

    • GET /api/knowledge/articles
    • GET /api/knowledge/articles/{slug}
    • GET /api/aeo/articles/{slug}?locale={locale}
    • GET /api/knowledge/search?q={q}&locale={locale}

    Structured errors

    API errors use RFC 9457 with application/problem+json. code is stable for programs, and resolution identifies the next useful step.

    application/problem+json

    Discovery documents

    Public MCP server

    A public MCP server runs at https://aprixity.run/mcp. It needs no login and is read-only. Agents find the published articles and the Engpass-Check there.

    Endpoint
    https://aprixity.run/mcp
    Transport
    Streamable HTTP
    Login
    none
    Access
    read-only

    Tools

    • search_aprixity_knowledge

      Search Aprixity knowledge

    • get_aprixity_article

      Read Aprixity article

    • list_aprixity_programs

      List Aprixity Academy programs

    • get_aprixity_site_guide

      Aprixity site guide

    • open_engpass_check

      Engpass-Check (bottleneck check)

    • evaluate_engpass_check

      Evaluate Engpass-Check answers

    Engpass-Check as an app

    open_engpass_check shows the Engpass-Check as a card in the chat when the host supports MCP Apps. You describe one process, mark where work piles up, and answer six questions. Fixed rules, not AI, turn the answers into the next check. Hosts without app support get the six questions as text. Some hosts ask before they first show the app or open a link.

    Data flow

    • The check runs in the host's view. Aprixity receives nothing from that view.
    • evaluate_engpass_check sends only the six fixed answers and two optional numbers: hours per week and hourly rate.
    • Requests to the server pass through Cloudflare and the Aprixity server like any website request.
    • The host, such as Anthropic or OpenAI, processes the chat under its own terms.

    Setup

    Claude

    In Claude: Customize > Connectors > + > Add custom connector. Enter this URL:

    https://aprixity.run/mcp

    ChatGPT

    In ChatGPT: Settings > Security and login, then turn on Developer mode. Under Plugins, add an app with + and enter the URL, including /mcp:

    https://aprixity.run/mcp

    VS Code

    File .vscode/mcp.json in your project:

    {
  "servers": {
    "aprixity": {
      "type": "http",
      "url": "https://aprixity.run/mcp"
    }
  }
}

    Cursor

    File .cursor/mcp.json in your project:

    {
  "mcpServers": {
    "aprixity": {
      "url": "https://aprixity.run/mcp"
    }
  }
}

    Codex CLI

    In a terminal:

    codex mcp add aprixity --url https://aprixity.run/mcp

    Menu names change. Check the current menu in your app.

    Capabilities and boundaries

    What is evidenced — and what a project must resolve

    Choose a system. Only connections with a documented relationship are shown.

    Demonstrated in the stated scope

    Read published content

    Concrete example
    Three documented GET operations return published articles and their AEO representation.
    Interface boundary
    Public unauthenticated read API; no write operation or access to private content.
    Prerequisites
    Published slug; supported locale and representation defined by the OpenAPI contract.
    Limitation
    Evidence covers this website’s published content contract, not a customer integration.
    Proof kind
    Maintained public contract

    Evidence state: Local OpenAPI contract read on 12 Sep 2026.

    Maintained evidenceOpenAPI 3.1.1API catalog
    Text overview of all matching capabilities
    • Read published content — Demonstrated in the stated scope. Maintained public contract. Public unauthenticated read API; no write operation or access to private content. Evidence covers this website’s published content contract, not a customer integration.
    • IMPACTS as a versioned file contract — Demonstrated in the stated scope. Public versioned source. Public file and method reference; no evidence of running automation. The contract describes a method. It does not prove customer outcomes or system availability.
    • Protected renovation-check MCP — Still to check. Public metadata observation. Separate protected service; not part of the website’s public REST API. Metadata proves discoverability. A successful authenticated tool call remains to be checked.
    • Connect a CRM or operational system — Project-specific work. No proof recorded. Project work after system and process review; not a generally available integration. Feasibility, write permissions, and operational responsibility are checked per system.

    Protected Sanierungs-Check MCP

    The Sanierungs-Check MCP is a separate protected service. It is not part of the public REST API. Clients start with the linked OAuth metadata and do not infer credentials from the main domain.

    OAuth protected-resource metadataOAuth authorization-server metadata