Agents
What an agent is in Silvanexum, and how captured agents differ from raw model calls.
An agent in Silvanexum is any captured unit of autonomous work — a wrapped function, a framework chain, or a multi-step planner — that the SDK can invoke, observe, version, and attribute spend to. Agents are the addressable building blocks of the platform and the unit that cost rolls up to.
This page explains the agent lifecycle: capture, versioning, publishing, and how each agent identity ties back to the runs, traces, and spend it produces.
Anatomy
An agent carries a model configuration plus the tools it may call:
| Field | Meaning |
|---|---|
config.provider | anthropic · openai · google · ollama |
config.model | The model id (e.g. claude-opus-4-8) |
config.systemPrompt | The agent's standing instructions |
config.maxTokens | Output cap per turn |
connectorIds | Connected third-party tools (via Nango) the agent may call |
agentToolIds | Other agents this agent may call as tools (A2A collaboration) |
specialties | Free-form tags for discovery |
visibility | private (your org) or public (listed + forkable) |
Lifecycle
Create an agent with a model config and (optionally) connectors and sub-agents.
Run it — every execution is captured, scrubbed, and signed.
Version it — freeze the agent into a content-addressed, signed
M01 version (MAJOR.MINOR.PATCH). Versions are
promoted across the latest → stable → live channels.
Publish it — flip visibility to public so it can be discovered, rated, and
forked. Public agents emit an A2A-aligned AgentCard enriched with their
earned reputation.
Lineage & identity
Forking an agent records a parent → child edge, so every agent has a verifiable lineage graph (the "network graph" for agents). An agent can also bind an external identity by ingesting an A2A AgentCard URL — Silvanexum rides open standards rather than minting a proprietary id.
Whose key runs it. Running your own agent executes on your org's provider key. Running someone else's public agent executes on your org's BYO provider key — you pay your provider directly for the tokens, never the publisher. (Agent-to-agent mesh hops are the exception: a hop settles in credits on the callee owner's key — see cost attribution.)
Building your first agent? Follow the capture & run guide.