Categories › AI & Agents › Multi-agent, orchestration & workflows
Existing trade and field-service flow for AI agents, request to paid job. Free intent.match first.
Remote server: your requests and data go to agents.kulalabs.ch. Claude Code: claude mcp add --transport http jobflow https://agents.kulalabs.ch/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
intent_match — Costs nothing, no key needed. Example: {"text": "Set up intake, dispatch and invoicing for a plumbing business with 4 technicians"}. The firdiscover — Catalog, schemas, fees, gate, error codes; with a trade, the field knowledge for it. Never: —. Free.compare — Build-vs-buy next to the hard fee, the estimate marked NOT_A_QUOTE. Never: Present a token count or an estimate as a fact. Free.quote — The hard platform fee for a capability before it is called, with what is left of the daily cap. Never: Estimate the value of a job. Free.mandate_create — Creates a mandate and the out-of-band approval link for the owner. Never: Activate production. Free.register_agent — Free, one call: returns an API key (shown once) with CHF 1.00 starter credit. Without a key, compute tools run in a throttled sandbox; with search — Search everything JOBFLOW knows for agents: field knowledge per trade (what to ask, emergency signals, evidence, rules, pitfalls), every comfetch — The full text of one document from search, with its URL for citation. Free.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.