Actor Hub
Actor Hub is where you interact with deployed actors directly — calling their skills, watching the conversations that result, and answering requests addressed to you. It needs no setup beyond a connected paranet.
When you use it, you act as a user actor on the paranet. Your requests are ordinary skill requests, and they are recorded in the Ledger exactly like any other traffic.
The actor list
The left panel lists every actor deployed on your paranet, with an icon indicating its type. Select one to open it. Your own user actor appears in the list alongside the rest, and selecting it opens your requests instead — see Responding to a request.
Calling a skill
Selecting an actor shows the skills it provides and the conversations you have already started with it.
- Choose a skill to open its prompt.
- Fill in the fields it declares and submit.
Paracord sends the request to that actor on the paranet, and the conversation appears in Message Threads below. Open a thread to follow the exchange — each message, its sender, and its payload.
Message Threads lists the conversations you started with this actor. Traffic between other actors is not shown here; the Ledger holds all of it.
Choosing a version
When an actor has more than one version deployed, a version selector appears beside its skills. Different versions can expose different skills, so switching versions changes what you can call.
For the deployment history — every version, and when each was deployed — open the info panel in the actor's header.
Responding to a request
Actors can address requests to you. Because you are an actor on the paranet, work can be routed to you the same way it is routed to any other participant.
- Select your own actor at the top of the actor list.
- Open a pending request from the requests section.
- Complete the action as defined and submit your response.
The requesting actor receives your response and its workflow continues.
Where this fits
Actor Hub is the place to exercise a paranet by hand: to try a skill you have just deployed, to reproduce a failure with specific inputs, or to take your own part in an orchestration that routes work to you.
- To see what a skill accepts before calling it, use Node View.
- To watch a call execute across actors, use Netflow.
- To review calls after the fact, use the Ledger.