AgentMesh
Talk to sales

Onboarding

Bring the agents you already have.

Onboarding is a family of AgentMesh platform agents that puts the agents you already run onto the mesh. Each agent keeps running where it is.

In this cartoon, a navy pilot boat leads three ships into a harbor. One ship is round, one is long and stacked with boxes, and one is a sailboat, and each one carries only a circle, a square or a triangle. The harbor pontoons form the mesh, with green nodes where they meet and three boats already moored. A green pilot robot on the pontoon holds a neat coil of line, and the line runs straight to a cleat.

Your agents come in as they are.

A harbor pilot boards a ship and guides it into port without changing the ship. Onboarding works the same way. A company might run eight LangChain agents, two Google agents and three Salesforce agents, and Onboarding brings all thirteen onto the mesh.

Onboarding never writes new agent logic, because building agents is the Builders' job.

Five agents make up the family.

  • Finder is a green pilot robot in a navy cap and peacoat that looks through a spyglass.

    Finder

    Finder lists every agent in your repos, cloud projects, Vertex, Bedrock, Copilot Studio and Agentforce. It also finds the agents that nobody listed.

  • Profiler is a green pilot robot that writes on a clipboard whose rows each start with a signal flag.

    Profiler

    Profiler reads each agent and drafts its Agent Descriptor. The Descriptor says what the agent does, what it refuses, what it records and which systems it reaches.

  • Connector is a green pilot robot on a dock that holds a neat coil of line in one hand. The line runs straight from the coil to a cleat on the dock.

    Connector

    Connector picks the path for each agent and does the work of putting it on the mesh.

  • Namer is a green pilot robot that paints a name in white letters on the side of a navy hull.

    Namer

    Namer claims a readable name for each agent under its owner's email, and then it tells the owner.

  • Checker is a green pilot robot that holds a checklist with green ticks and raises a green flag.

    Checker

    Checker confirms that each new agent answers, that its Descriptor matches and that its sign-in works. Then it writes the onboarding report.

The onboarding report shows where every agent stands.

Checker writes the report when the work is done. It shows how many agents were found and joined, which path each one took, and why any agent still needs a person.

This is an example onboarding report for the company with thirteen agents.

Checker wrote this report.

  1. Finder found thirteen agents from three vendors.
  2. Eleven of the thirteen agents joined the mesh.
  3. Eight agents joined through the adapter.
  4. Three agents joined through an A2A attachment.
  5. Two agents need a person, because each one signs in with a shared account that its owner must replace.

Each agent takes one of three paths onto the mesh.

  • The adapter runs beside code you control.

    Connector installs the adapter next to the agent in your own environment.

  • An A2A attachment brings in remote agents.

    Remote and SaaS agents join without any change inside the platform that hosts them.

  • The Builders take agents that the platform should run.

    Connector hands these agents to the Builders' Package Maker.

Finder only reads, and only the owner sees what it finds.

Finder runs inside your environment, or it uses read-only access that ends when the job ends. The inventory goes to the owner and to no one else.

Your agents can join the mesh from wherever they run.

Talk to us about onboarding your agents