GENVERNIUM DEVELOPER RESOURCES

Genvernium API, MCP, OpenAPI and SDK developer resources

Genvernium developer documentation for the public API, OpenAPI schema, MCP server, OAuth authentication, TypeScript SDK, Python SDK, and agent integrations. These resources describe Genvernium's public, read-only web surface for agents and integrations.

Genvernium developer documentation

OpenAPI discovery document — machine-readable public endpoints and their response types.

llms.txt — bounded product context, usage guidance, and operating limits.

OAuth authentication documentation — authorization-server metadata, PKCE flow, token exchange, and read-only workspace scope guidance.

Genvernium MCP server card — the public, read-only Model Context Protocol endpoint and machine-readable capabilities.

Published packages

@genvernium/sdk v0.1.1 — a dependency-free, read-only TypeScript SDK with the genvernium CLI. Install it with npm install @genvernium/sdk, then run npx --package @genvernium/sdk genvernium --help.

genvernium-sdk v0.1.0 — a dependency-free, read-only Python SDK with the genvernium CLI. Install it with pip install genvernium-sdk, then run genvernium --help.

Official Genvernium agent skills — read-only skills for public discovery, MCP integration, and SDK usage.

Genvernium on Smithery — the public MCP listing is published and points to the Streamable HTTP endpoint at https://genvernium.com/mcp. To publish a new release, use the Smithery publisher.

Homepage Markdown — request the homepage with Accept: text/markdown to receive a concise machine-readable overview.

Authentication boundary

Customer workspace APIs are authenticated and workspace-scoped. They are not anonymous public endpoints, and this public document does not claim to provide a public API key or OAuth client-credential flow. Do not place credentials in URLs, browser code, documentation, or agent prompts. Contact the Genvernium team if an approved integration requires a documented authenticated contract.

API reliability and versioning

Public discovery is read-only. Authenticated workspace write requests use an Idempotency-Key; long-running analysis work is queued with durable status and remains approval-gated. API errors are JSON with a code, message, status, and safe resolution when available.

The versioned workspace boundary is /api/v1. Breaking changes use a new major path. Deprecations are announced withDeprecation and Sunset headers before removal.