Jentic Mini: Self-Hosted API and Action Execution Layer for OpenClaw

Jentic Mini is a self-hosted API and action execution layer built specifically for OpenClaw setups, released this week under the Apache 2.0 license. It acts as a local execution broker between your AI agents and external APIs, solving credential management and security issues that typically arise when giving agents API access.
Core Problem and Solution
The tool addresses the common problem where giving agents access to external APIs requires hardcoding credentials, managing configurations, or leaking secrets into prompts. This approach doesn't scale, is insecure, and becomes difficult to manage. Jentic Mini sits between your agent and the outside world, storing credentials in an encrypted vault where they're never exposed to the agent.
Key Features
- Encrypted credential vault: Credentials are stored securely and never exposed to agents
- Scoped toolkits: Each agent gets one key that's individually revocable
- Automatic API discovery: When you add credentials, the system automatically imports from 10,000+ OpenAPI specs and Arazzo workflow sources
- Workflow persistence: When an agent discovers the right API chain, it can store that back as an Arazzo workflow. The next agent to run finds it through dynamic search without needing to figure it out again
- Open source: Fully open source under Apache 2.0 license
Practical Implementation
The source describes using Jentic Mini with an agent named Kitt: "My agent Kitt searches, calls, and chains APIs without ever seeing a raw credential. Credentials live in the vault; Kitt gets a scoped toolkit key." The workflow persistence feature proved particularly useful: "Kitt went pretty wild for the workflow persistence feature — once it figures out a sequence, it's reusable by any agent, permanently."
A concrete example provided: "Now when I'm running low on coffee, I let Kitt order me more — 3 API calls, zero credentials in Kitt's hands. That's the whole point."
This type of tool is useful for developers working with AI agents that need to interact with external APIs while maintaining security and scalability. The self-hosted nature means you maintain control over your infrastructure and data.
📖 Read the full source: r/openclaw
👀 See Also

Vibeyard: Open-Source Dashboard That Launches Claude Sessions from PRs, Issues, and Kanban Cards
Vibeyard is an open-source (MIT) home screen with draggable widgets for PRs, issues, kanban, and Claude sessions. Click any card to spawn a pre-scoped Claude Code session for review, fix planning, or resumption.

3D-Printed Clawd Mascot with ESP32-Powered Mochi Bot
A developer built a physical 3D Clawd inspired by the Claude Code mascot, with an ESP32-driven Mochi bot featuring a small display. Files and code available on MakerWorld and GitHub.

Claudigotchi: Physical Tamagotchi Device That Feeds on Claude Code Activity
Claudigotchi is a physical desktop creature running on an ESP32 with an LCD screen that connects to Claude Code via a plugin. The device's hunger system responds to coding activity, with visual states and sound effects that escalate when Claude is left idle.

Engram: Open-source memory layer for Claude Code and MCP clients
Engram is an open-source memory layer that works as an MCP server with any client like Claude Code, Cursor, or Windsurf. It stores unlimited memories with semantic vector search, achieves 80% accuracy on LOCOMO benchmark, and uses about 800 tokens per query versus 5K+ for file-based approaches.