AI workflow orchestration
I map the steps, API contracts, and data flows between a customer's systems and the models before I build the workflow.
Try it
Describe a request that takes more than one step. A planner breaks it into two or three steps, each step runs in order with the earlier results as input, and the page shows every step and its latency.
Public demo on Cloudflare Workers AI. Inputs are screened by Llama Guard 3 before any other model runs, requests are rate limited, and nothing here connects to a Luca or customer system.
How it works
- Trace one real requestI sit with the operators and follow one live request through their systems, recording every hop and its owner. That written trace becomes the step list, so we agree scope before I write any code.
- Fix the API contractI publish the versioned HTTP contract first, the way the public API at api.onluca.ai/v1 serves integrations behind bearer keys. Each data endpoint requires a named scope, and the OpenAPI document at /v1/schema lists the scope for each one.
- Encode the planI write the flow as ordered steps in the job engine's format: API call, condition, loop, wait, log, notify, set variable, and abort. In the engine's step runner, an API call step calls the platform's own routes and saves the reply for later steps. The engine stores these steps with each job, but nothing calls that runner yet, so running them is on the roadmap.
- Bind the toolsI expose each action as a tool on the tool bridge, and every tool call runs under a timeout. When a tool declares permissions, a caller who holds none of them is refused before the tool runs.
Tools
| Tool | What it does here | Status |
|---|---|---|
| Tool bridgeAvailable | Refuses a tool call when the caller holds none of the tool's declared permissions, and returns an error when a tool runs past its timeout. | Available |
| Public API, api.onluca.ai/v1Available | Gives integrations a versioned HTTP surface with bearer keys, a required scope on each data endpoint, and 120 requests per minute per key. | Available |
| Multi-provider model gatewayAvailable | Routes model calls through one gateway that holds the provider keys and records the provider, model, latency, and token counts for each successful call. | Available |
| Job engine and approval holdsEarly access | Queues jobs and holds infrastructure and data migration jobs for a person's approval. It does not run jobs itself, and nothing triggers its cron entries yet. | Early access |
| Cloudflare Workers AI (Llama)Demo only | Screens each request with Llama Guard 3, then plans and runs the steps for this page's demo on Llama models. It is not a customer deployment. | Demo only |
Available means shipped and in use. Early access means built but not generally available. Roadmap means designed, not built. Demo only means it powers the public demo, not customer deployments.
The write-up has every step of how I deliver this at a customer, with the tools and their status.
Read the write-up on gusit.deThe other answers
Built by Gus Assuncao of Gus IT LLC for a Forward Deployed Engineer application. Luca is the AI platform Gus IT builds and operates. Contact gus@gusit.de. Claude is a product of Anthropic PBC. Cloudflare and Workers AI are trademarks of Cloudflare, Inc. Llama is a trademark of Meta Platforms, Inc. Other names are trademarks of their respective owners. Gus IT LLC is an independent engineering firm and is not affiliated with or endorsed by these companies.