KONDEVS Website API
API by KONDEVS · rest
Two audiences. Public, no auth: the MCP endpoint (/mcp) exposes read-only tools over the published Content Hub, and /api/health reports liveness. Authorized partners only: the Publishing API (/api/content/) creates, updates and deletes articles and requires a bearer token issued by KONDEVS: request one at info@kondevs.com. Every page on this site also supports Accept: text/markdown content negotiation, so agents can read any URL as markdown without going through an API. Errors. Every /api/* error is JSON (Error): status, a stable code, message, a resolution hint and docs. The OAuth endpoints answer in the RFC 6749 format and /mcp in JSON-RPC 2.0. Versioning and deprecation. The Content API is version 1.1.0 (x-content-api-version on its responses, GET /api/content/version). Changes within major version 1 only add fields. A client may pin the major version with the X-Content-API-Version request header; another major version is refused…
Endpoint: https://www.kondevs.com/
Verification: observed. Source: crawl.
Capabilities (18)
- API index
- A2A agent: message/send
- Submit the contact form
- Publish a new article
- Article catalog in the Visibilio Connect shape
- Rebuild the article lists and counts from the stored articles
- Upload one image for an article (Visibilio Connect)
- The tags of the published articles (Visibilio Connect)
- Publishing API version and render capabilities
- Read one article
- Update an existing article
- Delete an article and its index entries
- Liveness probe
- How to obtain credentials
- Registration request (production: the instructions no credential; the…
- OAuth 2.0 token (client_credentials)
- Not supported (no server-initiated SSE stream)
- MCP Streamable HTTP endpoint (JSON-RPC 2.0)