Nibleaf public OpenAPI
A typed OpenAPI 3.1 contract for reading published sites, pages, search results, changelogs, sitemaps, and agent indexes. Every operation has a unique operationId and description.
Open openapi.jsonDevelopers and agents
Nibleaf developer resources
Discover the supported public reader API, machine-readable product files, Markdown negotiation contract, and command-line tooling without guessing private dashboard routes.
Predictable entry points
Agent-readable content
Start with llms.txt, request canonical marketing URLs with Accept: text/markdown, and use each published site’s own sitemap and llms files for recovery and retrieval.
Read llms.txtRead-only MCP control plane
Source main includes project-bound MCP resources and tools for content, search diagnostics, usage, add-ons, integrations, operations, and themes. Scoped keys can expire; write operations are not exposed.
Read the MCP guideOfficial Nibleaf CLI
The @nibleaf/cli package inspects a Nibleaf site’s machine-readable endpoints and fetches canonical pages as Markdown for scripts and agents.
View the npm packageCall Nibleaf from an agent
- 1. Read /llms.txt to choose the right product or documentation resource.
- 2. Send Accept: text/markdown to a canonical Nibleaf marketing URL when clean page content is needed.
- 3. Read /openapi.json before calling the public reader API; preserve typed parameters and operation IDs.
- 4. Treat a 404 as a missing path and recover through the sitemap or llms index.
CLI quick start
npx @nibleaf/cli inspect https://nibleaf.com
npx @nibleaf/cli fetch https://nibleaf.com/developersThe CLI uses standard HTTP endpoints and does not collect credentials. Its inspect command checks status, content type, OpenAPI, llms, sitemap, Markdown negotiation, and real 404 behavior.
Authentication and support boundary
Public published sites require no credentials. Private reader sites use their configured reader session and intentionally return 404 to unauthorized callers. Dashboard endpoints use an authenticated browser session and are not a supported third-party write API. Do not send session cookies or secrets to the CLI. The MCP contract in source main is a separate project-bound, scoped, read-only surface; it is not a dashboard-session write API.