Self-hosted API execution layer that sits between your agent and the outside world. Your agent says what it wants to...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
OpenClaw
Model
Multiple
Fastest way to find out if jentic-one belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/jentic/jentic-one ~/.claude/agents/jentic-oneRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/jentic-oneNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ jentic-one/ ← installs here └─ settings.json
Self-hosted API execution layer that sits between your agent and the outside world. Your agent says what it wants to do. Jentic One handles the how — finding the right API, injecting credentials at runtime, and brokering the request
Source: GitHub repository
Source check: No source check recorded
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.