AiSynth
English
Start creating
The agent studio

aisynth crews, patched like instruments.

Compose visible agent workflows, route signals between tasks and press play. aisynth turns a complicated arrangement into one clear system you can inspect, adjust and run. Compose a crew, then press play.

Try a crew on your workflow patch console / live handoff
No setup here · one tap to continue Open the full studio
Webhook in HTTP out Resend Anthropic OpenAI Gemini xAI Cron runs REST API Slack Telegram RSS → digest Webhook in HTTP out Resend Anthropic OpenAI Gemini xAI Cron runs REST API Slack Telegram RSS → digest
The rack

Six modules, one signal path

Each module has one job. Patch them together and the whole workflow becomes a single instrument you can inspect, adjust and run again.

CH 01

Patch-bay canvas

Lay agents and tasks on a board, give each one a role and draw the connections without glue code.

CH 02

Signal routing

Send one task into the next, branch, merge and fan out across the services your workflow touches.

CH 03

Any model per voice

Assign the right model to each agent individually, with your keys protected until the moment of a run.

CH 04

Run-metered work

Every pass draws from one clear balance, so the cost of an arrangement stays visible before it moves.

CH 05

Play it remotely

Trigger a saved patch from your own code, on a schedule or when an event reaches the right endpoint.

CH 06

Locked credentials

Service credentials stay encrypted, scoped to their connection and touched only while the patch runs.

CH 01
patches ready on the shelf 330+
CH 02
instruments agents can play 120+
CH 03
model providers on one patch bay 5
CH 04
seats or recurring renewals No
Studio session

Watch one arrangement go from patch to payoff

Five short chapters: the same crew you would build, played end to end.

arrangement / morning digest ready to play
S
Sampler

Gather the week's useful signals

claude-sonnet
A
Arranger

Shape the findings into a clear brief

gpt-mini
M
Mastering

Polish the final cut for delivery

gemini-pro

A researcher, a writer and an editor take their places — each with its own model behind it.

The session

From empty rack to a running arrangement

01

Patch

Place agents on the board and give each one a role, a goal and a model.

02

Route

Draw the signal path between tasks and plug in the services they touch.

03

Play

Run the arrangement once, on a schedule or straight from the API.

04

Review

Open the ledger and read exactly what the pass used, line by line.

Work units

One balance powers every patch

Choose the working lane that fits the arrangement. Runs draw the balance down; nothing renews in the background.

CH.01

Starter

Light lanefor first passes
  • All model providers
  • Sequential process
  • Built-in actions
Try Starter
CH.02

Maker

studio pick
Steady lanefor weekly work
  • Hierarchical routing
  • Public API access
  • Crew memory
Try Maker
CH.03

Pro

Deep lanefor layered crews
  • Everything in Maker
  • Priority queue
  • Scheduled triggers
Try Pro
CH.04

Scale

Wide lanefor connected teams
  • Unlimited API keys
  • Priority queue
  • Low-balance alerts
Try Scale
CH.05

Studio

Full lanefor the whole mix
  • Everything in Scale
  • Team invitations
  • Best working rate
Try Studio

Bigger lanes keep the flow steady — and the balance never expires.

FAQ

Before you plug in

What do run units cover?
Everything a run consumes — model calls, connector actions and engine time — converted into one clear unit for the whole studio.
Do runs renew automatically?
No. You choose when to continue, and a run only uses the balance already available for that arrangement.
Which models can my agents use?
Bring your own keys for Anthropic, OpenAI, Gemini, xAI or another compatible endpoint, then assign a model to each agent.
How does a run move through the patch?
Each task hands its output to the next connected task, so the path stays visible from the first signal to the final result.
Can I bring my own workflow?
Yes. Start with a ready patch, connect your own services or use the API to trigger an arrangement from your existing stack.
How auditable is the spend?
Every pass leaves a readable ledger, with the path, actions and run usage recorded line by line for review.

Patch your first crew today.

Start with a simple arrangement, shape the signal path and see how the whole workflow feels when it runs together.

S Starter routea first session's worth of room ▶ M Session routespace for a week of arrangements ▶ L Studio routethe full mix for connected crews ▶
Open the studio

press any key — runs only, nothing recurring

Start creating
Start creating