Agent product files
A product file with $type Agent sells one agent to each customer; it names the Role the agent fills and the Verbs it may call.
A product file with $type: sells one Agent to each Customer. It names the Role the agent fills, and that Role file holds its instructions, Limits, approvals and channels.
products/renewals.mdxLeaseline's renewal agent, one per property manageragents/customer/success-manager.mdxthe Role it namessuccess-manager.test.tsits eval cases
Reference
| Key | Type | Holds | Required | Status |
|---|---|---|---|---|
$type | list | One or more of App, API, Agent, Dataset, Service | required | live |
nouns | Noun names | The Nouns it exposes; a Dataset holds Things of exactly one | live | |
verbs | Verb ids | The Verbs a Customer may call | live | |
interfaces | list | The Interfaces it ships on; every kind by default | live | |
role | Role path | The Role in agents/ its agent fills: instructions, Limits, approvals, channels and eval cases | required | live |
Examples
Minimal
---
$type: [Agent]
role: customer/ success-manager
---Leaseline
---
$type: [Agent]
role: customer/ success-manager
nouns: [Lease]
verbs: [Lease.notify, Message.create]
---
No renewal slips past its date.What it builds
The SoftwareBuilder compiles the file with its Role.
- an agent per Customer on acceptance, minted in that Customer's Tenant
- one Tool per Verb in
verbs, and the agent card at/agents.json - the eval gate: every case in the Role's test file passes before an Offer publishes or a Version ships
Good to know
- The book is an agent sold as a service; its reference lists every Verb.
- An Offer sells the agent from an offer file, billed on graded work.