Last reviewed:
View source and documentationWho it is for
TypeScript developers who want to publish paid agent capabilities or integrate autonomous services without designing every discovery and payment primitive from scratch.
How it works
Define a capability
A developer describes what the agent or service can do and the input it expects. The public interface should be narrow enough for another agent to call predictably.
Attach commercial terms
The service can expose paid access through integrations documented by the project. Budget enforcement, wallet custody, and policy remain deployment responsibilities.
Publish and operate
Consumers call the deployed capability and receive its result. Operators still need logging, evaluation, rate limits, and version management appropriate to the service.
Published evidence
- The framework source and package history are publicly inspectable on GitHub.
- The repository provides the current implementation record, issue history, and usage examples.
- No usage, revenue, or reliability metric is asserted here without a reproducible source.
Limitations
- Open-source software still requires secure deployment and monitoring.
- Payment support does not validate an agent's output.
- APIs and supported integrations can change; pin versions and consult the repository before shipping.