Structured baseline result
Outputs such as result, profile_detected, readiness_level, missing_required_blocks, and risk_flags.
HREVN Developers
Technical resources and the shortest first-test path
This page exists so that a developer, crawler, or technical agent can understand HREVN without having to traverse multiple links before seeing the operational core.
It gathers the live runtime, MCP server, public surfaces, installable artifacts, and the minimal path for running a first baseline check.
What HREVN returns
Remedy payload
A structured remedy_payload that explains what remains missing before proceeding instead of leaving a generic warning.
Receipt-aware continuity
A check_id, verifiable evidence, and a continuity point that can be reused after interruptions, handoffs, or restarts.
Runtime and first test
Managed API
Live backend behind https://api.hrevn.com for baseline checks, bundle generation, and verification.
MCP server
Structured access to the same runtime through MCP, published as both a repo and an installable package.
Shortest technical path
The minimal route is to install one surface or the MCP server, configure the API key, and run a baseline check against the live runtime.
Public installable artifacts
Google / Genkit
Public npm package for the Google / Genkit surface.
OpenClaw
Public PyPI CLI for a local-first path.
Anthropic
Public runner for the Claude Code-facing surface.
Codex
Public CLI for the Codex helper-first surface.
MCP server
Public reusable MCP server across different surfaces.
Public surfaces and honest status
Anthropic
Repo and installable runner for a path built around skills, a local runner, and MCP.
Codex
Repo and installable CLI for an already executable helper-first alpha.
Google / Genkit
Repo plus public npm package over the live HREVN runtime.
OpenClaw
Repo plus PyPI CLI with local-first framing and real end-to-end validation.
Kiro
Public power alpha with MCP, steering, and example hooks. Current status: honest exploration, not a finished native integration.
Next step
If you arrived through technical discovery, the right path is usually: review the technical overview, open the surface closest to your environment, and run the first baseline check against the live runtime.