How it works
From one useful result to live work you can improve. Seven steps.
No step needs code until the one where your product connects. Each step says what you do, what the platform does, and what you have afterwards.
From one useful result to live work you can improve. Seven steps.
-
Step 1 of 7
Choose one useful result
Write the outcome in a sentence a customer would recognise. “Answer a billing ticket with the right queue and a draft reply” is a result; “use AI for support” is not.
- You do
- Name a project and describe the result
- Vendor.sh does
- Creates the project with Development, Staging and Production
- You get
- A place for the work, separated from every other project
-
Step 2 of 7
Build the path visually
Place the agents, tools and branches on the canvas in the order the work happens.
- You do
- Draw the graph and write each agent’s instructions
- Vendor.sh does
- Saves a draft and checks that every step is connected
- You get
- A path the whole team can read
-
Step 3 of 7
Connect the correct accounts
Choose how each model is reached and which accounts your tools act as.
- You do
- Pick a provider route and add tool connections
- Vendor.sh does
- Stores credentials outside workflow content
- You get
- Connections the draft can use, and nothing else
-
Step 4 of 7
Try real examples
Run the draft on inputs taken from real work, including the awkward ones.
- You do
- Start try runs in Development
- Vendor.sh does
- Records every step with its inputs, tokens, latency and cost
- You get
- Evidence of how it behaves before anyone depends on it
-
Step 5 of 7
Release a checked version
Score it against saved examples, then release the version you tested.
- You do
- Run an evaluation and release
- Vendor.sh does
- Freezes the version so it cannot change underneath a caller
- You get
- A numbered release that Staging and Production can point at
-
Step 6 of 7
Connect the product
Your backend calls the deployment with a limited service key.
- You do
- Create a service key and send the first request
- Vendor.sh does
- Accepts the run, queues it, and streams its steps
- You get
- Live requests from your product, safe to retry
-
Step 7 of 7
Review and improve live work
Read what happened in production and turn it into the next release.
- You do
- Read runs, traces, and cost against budgets
- Vendor.sh does
- Keeps runs, costs and changes on the record
- You get
- The next version, based on what really happened
See how your backend sends work to Vendor.sh.
Use the integration guide when you are ready to connect a live application.