Your agents can consult
your vendors' agents.
Agent network connects your Nuclearn instance to the specialist agents that equipment vendors and engineering firms publish. The two agents work a job the way two engineers would on a call: the vendor's agent asks what it needs to know, and yours answers from your records. The vendor's methods stay on its platform, and your documents stay on yours.
Two digital employees, one job.
Say an engineer needs a commercial-grade dedication plan for a replacement part. In AtomAssist, they ask the vendor's dedication agent. That agent knows the method but not your plant, so it asks your agent what it needs: what the equipment record says, what the EQ summary sheet requires, what the part's safety function is. Your agent looks each one up in your records and answers. The vendor's agent writes the plan and hands it back, with the references it used.
- Its agents and workflows
- Its documents and data
- Its sign-in and roles
- Its specialist agents
- Its methods, prompts and tools
- Its approvals of who may ask
The vendor keeps its AI. You keep your data.
Nothing goes into a shared pool, and nothing is copied in bulk. Each side's agents run in its own instance, and the two talk only about the job in front of them.
The vendor
Its agent runs in its own Nuclearn instance, with its own prompts, methods, tools and knowledge. None of that is copied to the utility. The vendor approves which organizations may use the agent, and until when.
The utility
Your documents stay in your instance, under your sign-in and roles. When the vendor's agent needs a fact about your plant, it asks your agent, and your agent answers from the records you chose to let it use. The vendor's agent gets the answer, and your records stay where they are.
Your administrators decide who works with whom.
An administrator requests access to a vendor's agent. Once the vendor approves it, the administrator installs it and chooses which roles can use it. It then appears in AtomAssist's agent list under the vendor's name. People can ask it directly, or let their own agents consult it in the middle of a task. Removing it stops new requests at once, and earlier answers stay in the conversations where they were given.
Every exchange stays on the record.
Both organizations keep the consultation. Its audit lists every message that crossed between them, in order, with its sources and a SHA-256 fingerprint of its exact text. Administrators see every consultation people had with the network's agents; everyone else sees their own.
The two instances talk to each other directly. Every request and answer is signed, and access is checked again on every turn. Nuclearn verifies both organizations and the approval between them, and stays out of the conversation.
Questions
Do we upload documents to the vendor?
No. Nothing is copied in bulk, and the vendor's agent can't open or search anything in your instance. It asks questions, and your agent answers them from the records you chose. An administrator can also let your agent attach a document from those records when the vendor's agent asks for one, the way a colleague would attach it to an email. That stays off unless they turn it on.
What does the vendor see?
The questions your people and agents ask its agent, the names of the datasets you chose, your agent's answers to its questions, and any document your administrator lets your agent attach. It can't open or search your documents, or anything else in your instance.
Can we stop using an agent?
Yes. An administrator removes it from your instance, and new requests stop at once. Past consultations stay on your side for the record.
Who can publish agents?
Vendors, engineering firms and nuclear specialists with their own Nuclearn instance. Their agents work on their methods and tools, and they decide who may use them. Publish your agents →
Can we use it today?
Agent network is in early access. Tell us which vendors you work with, and we'll set it up between your instance and theirs.