TypeScript and Python clients
Bring your own agent. Keep it governed.
Thin TypeScript and Python clients for the governed actions API. Your agent asks for an action. The kernel decides, then runs it with its own credentials.
Clients
For the agents you already run
If your agent is your own code, the clients are how it asks OrchKernel to act.
01
TypeScript client
For agents written in TypeScript or JavaScript.
02
Python client
For agents written in Python.
How it works
Your code asks. The kernel decides and acts.
The clients are thin on purpose. Identity, policy and credentials stay in the kernel.
- 01Your agent gets its own identity
An admin registers it. It acts for a person and never has more than that person.
- 02It asks for an action
A refund, an email, a record change: through the client, to the governed actions API.
- 03The gate answers
Allowed, needs approval or denied, with the reason.
- 04OrchKernel runs it
With its own credentials, once. Your agent never holds your vendor keys.
Frequently Asked Questions
Put an agent on real work, with people in charge
Design partners run one real workflow on OrchKernel and work directly with the engineers building it.
OrchKernel is source-available and self-hosted.