Hey Product Hunt 👋
Message from the CEO of Gentic:
I’m Sean, co-founder of Genetic. We’ve spent the last 18 months working on a problem that has plagued anyone building AI agents: How do you allow an agent to call real APIs without leaking credentials or losing control?
The typical pattern today is this: you hardcode the API keys into the prompt, write bespoke wrapper functions for each service, and hope nothing gets logged, cached, or spoofed. It works for demo. It breaks down in production.
What does genetic money actually do?
It’s an API execution layer — a FastAPI server that you host yourself in Docker — that sits between your agent and every API it needs to call. The architecture is straightforward:
Find out.: Your agent queries the BM25 full-text index of 10,000+ API specs and 380 Arazzo workflow sources from our public catalog. It finds the correct operation without you having to write a single wrapper.
execution: Genetic Money Brokers Application. Credentials are stored in a Fernet-encrypted local vault and injected at runtime. The agent never sees them. They are never returned by the API.
Toolkits: Each agent receives a scoped toolkit key (tk_xxx) with its own credential bundle and access policy. One key per agent, can be revoked individually. If something goes wrong, you kill the key. done
Observe.: Complete execution traces and audit logs. You can see exactly what your agent said, when, and what came back.
Why we made it
We are already running a hosted genetic platform (with semantic search, lambda-based brokering, SOC 2-grade security) and we are a certified connector in the cloud. But we kept hearing the same thing from developers: “I want to run it myself.” So we built mini, same API level, self-hosted, Apache 2.0 licensed.
A command to start is:
$ docker run -d --name jentic-mini -p 8900:8900 -v jentic-mini-data:/app/data jentic/jentic-miniAdd your API credentials through the UI on localhost:8900, and the specs are automatically imported from the public catalog. Your agent authenticates with the toolkit key via the X-Gentic-API-Key header and immediately begins searching and executing.
What’s next?
This is early access. There will be rough edges. We’re sharing it now because we want the community building agents (OpenClaw, NemoClaw, LangChain, CrewAI, whatever your stack is) to test it, break it down, and tell us what’s missing.
Would love to hear which APIs and workflows you want to connect first.