Skip to main content
MonoAPI is the API-specification ingestion edge of the Monomento stack. It reads a JSON specification from HTTP or a local file, renders the parts an agent most often needs, and stores that Markdown in Monomento as doc_type=openapi unless indexing is disabled. Published contract: monoapi 0.2.1, OpenCLIs build 2026-04-12-113646. The installed-state row, immutable payload, public CDN pointer, and CDN release metadata agree on this identity. The exact installed payload was also code-signature verified on macOS.

​
Quick Start

Use --no-index first when the specification is unfamiliar. It proves that the document parses and lets you inspect the generated Markdown without changing the shared search index.

​
Published Command Surface

The current public build has 2 operational root commands plus help and version aliases. There is no direct MCP schema or endpoint-execution command. MonoAPI describes an API; it does not call the operations in that API and it does not manage credentials.

​
Parser and Help Boundary

MonoAPI uses a small hand-written dispatcher, not a nested argument parser. There is no command-specific help surface in the published build:
Do not probe a subcommand by appending --help; for fetch-like tools that token can be interpreted as real input. Use bare monoapi, monoapi help, or this page.
Repository HEAD also contains a docs [topic] dispatcher for a future build. The immutable 0.2.1 / 2026-04-12-113646 payload rejects docs with a non-zero exit, so automation must not depend on it yet.

​
What the Converter Preserves

The converter is intentionally compact rather than exhaustive. Important limits:
  • Input is JSON only. YAML must be converted before MonoAPI reads it.
  • Swagger 2 JSON path operations can be rendered, but Swagger 2 securityDefinitions, definitions, and body-schema conventions are not a full-fidelity OpenAPI 3 translation.
  • $ref values are reduced to their final path segment. References are not recursively or cross-file resolved.
  • HEAD, OPTIONS, and TRACE operations are not emitted.
  • The complete specification and generated Markdown are held in memory. HTTP reads have a 30-second client timeout.
Treat the generated reference as an orientation layer, then compare important claims with the service’s live behavior and primary documentation.

​
Identity, Deduplication, and Storage

The stored key is the input string supplied to fetch: the URL or local path is not canonicalized first. Deduplication is therefore scoped to that stored path. Re-fetching identical content at the same path is skipped; changed content replaces it; two different aliases can remain separate documents. MonoAPI uses Monomento’s shared global database resolution:
  1. $MONOMENTO_HOME/monomento.db when MONOMENTO_HOME is set;
  2. otherwise ~/.monolex/monomento.db when it exists;
  3. otherwise the legacy Monolex application-support database when present.
Use Monomento for cross-source search and section reads.

​
Published Platforms

These six platform entries come from the immutable CDN meta.json, not from an inferred cross-platform claim.

​
Relationships

The normal evidence flow is monoapi fetch, monomento search, then monomento read for the section that owns the endpoint or schema.