Orchestrations
A Promptev orchestration is a team of your existing AI agents led by one of them: the lead hands each part of a job to the agent built for it, collects the results and returns one answer, with a person’s sign-off where you ask for it.
How it works
Step 1
Build the team from agents you already have. The lead decides which agent to call, in what order, and which can work at the same time. A team member can lead a small team of its own.
You reuse agents you already built and tested.
Then give the team its work.
Step 2
Run it from the App, from another agent, or from its callable URL. Inputs can be text, dates, numbers, choices or files, and files are read automatically, scanned pages included.
The same run starts from a button, an agent or your own systems.
Then follow it and decide what leaves.
Step 3
The run page shows each agent’s work in order, with its cost. Where you ask for it, an assigned reviewer signs off before the result is delivered, or asks for changes. You can cancel a run at any time.
A person decides before the result goes out.
Built to finish
A team run can take minutes and many steps. If a server restarts in the middle, the run is picked up again where it was, and tool calls that already finished are not repeated. In the rare case a step may have run twice, the run page says so.
Example
A legal team’s intake form sends a supplier contract to the orchestration’s callable URL. The lead asks the extractor for the parties, dates, renewal and liability terms, has the policy checker compare them with the team’s playbook, and has the drafter write the reply.
The run stops for the assigned reviewer. She asks for one change, the lead works again with her note, and she signs off. Only then is the reply delivered.
Questions
Several AI agents working on one job. In Promptev, a lead agent splits the job, hands each part to the agent built for it, and combines the results into one answer.
Runs are durable. If a server stops, the run is picked up again and carries on, and tool calls that already finished are not run again. You can also cancel a run yourself; the steps that finished are kept.
Yes. You can require an assigned reviewer to sign off before the result is delivered. The reviewer can approve it or ask for changes, and the lead works again with their note.
Give the orchestration a callable URL. Send it a request, with files if the orchestration takes them, and it runs the same way as a run started in the App.