# Aprixity Developer Resources | Public API

> Source: https://aprixity.run/en/developers

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 three supported public read operations. These operations require no authentication.

[/openapi.json](/openapi.json)

## Public read operations

-   `GET /api/knowledge/articles`
-   `GET /api/knowledge/articles/{slug}`
-   `GET /api/aeo/articles/{slug}?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

-   [OpenAPI 3.1.1 — Open](/openapi.json)
-   [RFC 9727 API catalog — Open](/.well-known/api-catalog)
-   [llms.txt — Open](/llms.txt)
-   [Authentication boundary — Open](/auth.md)
-   [Aprixity content skill — Open](/.well-known/agent-skills/aprixity-content/SKILL.md)

## 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 metadata](https://sanierung-mcp.aprixity.run/.well-known/oauth-protected-resource)[OAuth authorization-server metadata](https://sanierung-mcp.aprixity.run/.well-known/oauth-authorization-server)