Quick start
Start with the JSON service index or load the OpenAPI document into an agent that understands OpenAPI 3.1. All documented operations are idempotent reads.
curl --fail-with-body https://nodsapp.com/api
curl --fail-with-body https://nodsapp.com/openapi.jsonAuthentication and use
Authentication is not required. The service exposes published reference content only; it has no write, account, payment, camera, or user-data operations. Respect normal HTTP caching headers and cite each article’s canonical HTML URL when using it as a source.
Content representations
Article and glossary Markdown mirrors use predictable URLs and include canonical metadata, bylines, publication dates, questions and answers, and source links.
GET /articles/{slug}/index.md
GET /glossary/{slug}/index.mdStructured errors
Machine endpoints return RFC 9457 Problem Details as application/problem+json. Alongside the standard fields, code, message, and resolution provide stable handling and a concrete recovery hint.
{
"type": "https://nodsapp.com/developers#error-resource_not_found",
"title": "Resource not found",
"status": 404,
"detail": "No published NODs article matches this URL.",
"instance": "/articles/example/index.md",
"code": "resource_not_found",
"message": "No published NODs article matches this URL.",
"resolution": "Check https://nodsapp.com/llms.txt for current article slugs."
}resource_not_found
The requested endpoint, article, or glossary slug is not published. Refresh the service or agent index before retrying.
method_not_allowed
The resource is read-only. Use a method listed in the response’s Allow header.
temporarily_unavailable
The edge could not render a machine response. Honor Retry-After and retry later.