- A Tilde Cloud organisation, and an agent registered in it. See Anatomy of an agent.
- The
tildeCLI, and Git.
1. Create the project
In Ontology, select Create project, and name itsupport. Open it, select Environments, then Create environment, and name it production. On the environment, select Issue deploy token, and copy the token.
2. Write the ontology
Create a repository with three files.tilde.toml
ontology/package.json
@tilde/ontology is not listed: Tilde provides it when it builds the project, so you never install it yourself. List only the packages your own code imports.
The ontology ships two customers as reference data, so you need no connection yet. It has one object type, two reads, one action, and the policies that let people and agents use them.
ontology/ontology.ts
3. Deploy it
Commit, and deploy with the token from step 1.4. Give the agent the ontology
1
Connect the environment
In Tools, select Connections, then Tilde Catalog, and choose Tilde Ontology. Select Add account, and enter the
production environment’s ID.2
Add the tools
Open your agent in the Agent Registry, select Tools, then Add tool, and choose the connection. Switch on
listCustomers, customerOverview, and setNotes.3
Allow them
In the agent’s Capabilities tab, add the three tools to
tools.invoke.5. Try it
Ask the agent:listCustomers to find Acme’s id, customerOverview with {"key": "acme", "input": {}}, and then setNotes with {"key": "acme", "input": {"notes": "Asked about SSO."}}. Each call is decided by your policies, for the agent and for the person it serves. Review the calls in the agent’s Sessions tab.
Next steps
Bring in real data
Replace the reference data with a pipeline and a connection.
Tighten the policies
Limit agents, mask fields, and require approvals.
Call third parties
Have actions update the systems you already use.
Add a space
Show the same reads and actions to people in Live.