How calls compose

The reference for every call on this page is Compose your own.

Three promises: the steps, the output, the outcomeCopy Anchor Link

A Workflow promises its steps run. An agent task also promises its output passes an Evaluator, or it is redone or free. A Service promises the outcome under an Outcome Contract.

The kind comes from the promise, never from the steps. Build a verified list asks a model whether each company fits, and still promises only that its steps run. Booked first calls runs that same Workflow inside it, and promises held meetings.

Each kind is built from the one belowCopy Anchor Link

Read down: a Service orders agent tasks, an agent task reads from a Workflow, and a Workflow's steps are Data calls. Each example carries its own price, and cost adds up the chain.

Control: you, a goal, a Play or a strategyCopy Anchor Link

Control is the other axis. Any kind can be called by you, planned by a goal, ordered every week by a Play, or chosen by your strategy.

Every Workflow, agent task and Service, by stageCopy Anchor Link

Each is one call at the price on its card, at the size the card states. Your time is what it asks of you: inputs, picks and review.

Get foundCopy Anchor Link

Start conversationsCopy Anchor Link

Make the saleCopy Anchor Link

Keep customersCopy Anchor Link

Grow each customerCopy Anchor Link

Earn referralsCopy Anchor Link

Every one keeps the same edgesCopy Anchor Link

Whatever its kind, a composed call behaves the same way at the edges, so an agent that can call one can call them all.

• Priced before it runs. try returns the plan and the most each step can cost, and spends nothing.
• One Event. It emits one Event named for its Verb, such as Audience.built, carrying each step's cost.
• Idempotency keys. Each step's key is the parent key plus the step and the item, so a retry never charges, sends or posts twice.
• Retries, then fallback. A failed step retries three times, then a data step tries its next route (Data).
• A cost cap, then resume. It stops before a step would cross maxCost, and returns what it has with a resume link.
• Skipped, with reasons. One item that fails lands in skipped with its reason, and the rest of the call goes on.

Some return in minutes, some wait weeksCopy Anchor Link

How long a call takes is a third question. A call that waits on the world, such as an index or a reply, runs as send and costs nothing while it waits.

Compose your own from the calls you useCopy Anchor Link

Chain any calls into one call of your own, and name it on a hub Noun in your own namespace. Your agent, API, CLI and MCP server all get it, priced before it runs.

import { $, workflow } from 'startup-builder'

export default workflow({
  name: 'hiring-brokers',
  verb: 'Audience.buildHiring',
  maxCost: 3,
  execute: async (ctx) => {
    const hiring = await ctx.step('hiring', () => $.Organization.find({ where: { hiringFor: ['leasing coordinator'] }, maxCost: 0.1 }))
    return ctx.step('list', () => $.Audience.build({ from: hiring, size: 50, maxCost: 2.5 }))
  },
})

Add grade: { evaluator, passWhen, remedy } and it deploys as an agent task. Add contract with its done Event, price and remedy, and it deploys as a Service. Compose your own covers each.