-
Notifications
You must be signed in to change notification settings - Fork 95
Description
I love agentapi!
Is there any interest in client libraries and/or CLIs for it? Arguably these are not necessary, as the exposed REST API is so clean and simple, and one can simply use libraries like requests (for us python developers) or command line tools such as curl. However, having a library and CLI tools might still be useful, and it might also be useful to bundle a few higher level operations, such as performing end-to-end workflows (analogous to claude -p). And a simple CLI plus skills may turn out to be a better approach for agent to agent communication compared to MCP or A2A.
One reason I ask is that a few months ago we embarked on an attempt to build a python library that has similar goals to agentapi:
The approach is a little different - it is not intended for interactive use, but for end-to-end workflows, and it wraps CLI calls rather than terminal emulation. But it is far less developed than agentapi, and had we known about it (for some reason it didn't show up in our deep research queries) we would have built on it.
We are likely to replace the internals of metacoder and switch to agentapi:
metacoder may live on as a layer on top, providing a light CLI shim plus a bridge to deepeval. But if y'all are already planning on a CLI layer then this might be redundant too. In which case we'd much rather reuse than write our own!