Quickstart
The fastest path: write a YAML file, point an Agntz SDK at the directory, call it. No server, no signup, no infrastructure. The YAML is shared between TypeScript and Python; the client code follows each language's conventions.
Install
See Models & providers for the full list of supported providers.
1. Create an agent
The agent's id is how you'll address it from code. kind: llm means a single model call. With no inputSchema, the agent takes a plain string, accessible in templates as {{userQuery}}.
2. Run it
That's it. The SDK parses every .yaml file under ./agents, validates it against the schema, registers it with the runtime, and exposes the same client.agents.run, client.runs.list, and client.traces.get surface as the hosted client.
3. Stream or inspect
TypeScript local runs expose token deltas for LLM streaming today. Python local runs expose start and complete events in this first slice; the hosted Python client streams the worker's SSE events.
4. Use the same call against the hosted cloud later
When you outgrow embedded mode — durable run history, multi-user isolation, agent management UI — switch constructors and keep the same resource shape:
The agents.run, runs.list, and traces.get calls work across local and hosted clients. YAML manifests move to the hosted registry; in-process local tools become MCP servers or HTTP endpoints.
Next steps
- Add structured I/O. Declare an
inputSchemaandoutputSchemato type-check the agent's contract. - Add tools. Wire up HTTP, MCP, or local tools.
- Chain agents. Compose multi-step workflows with sequential and parallel pipelines.
- Persist sessions. Use SQLite for durable conversation history.