Deterministic workflows
AI understands the request. Your business logic decides what happens.

Setu is the intelligence layer between customer conversations and your business systems. Understand intent. Extract the required information. Execute verified workflows through your existing APIs.
Natural language → Intent → Workflow → Verified action
See customer requests rotate across Hinglish, English, Bengali, Tamil, Marathi, Gujarati, Spanish, and French. Pick a sample and run the demo workflow.
Setu, or सेतु, is Sanskrit for bridge. That's what it is: an API layer between AI conversations and business systems. Setu understands customer intent, extracts the information required by your workflow, and executes verified actions through your existing APIs.
It is not an autonomous agent. It is not a generic chatbot. It is API-first infrastructure for turning conversations into controlled business execution.
Every request follows the same six-step path. Deterministic where it matters, language-aware where it counts.
Setu accepts raw customer messages in English, Hindi, Hinglish, and the multilingual languages listed below.
"Payment ho gaya but order nahi bana"
Setu classifies against the intents you have declared in your workflow.
payment_status
Setu extracts the entities required by that workflow.
payment_reference order_id
Setu walks the declared workflow: fetch inputs, evaluate conditions, choose actions.
check_payment → check_order → reconcile
Setu calls your existing APIs. Semantic actions map to your OMS, CRM, or ERP endpoints.
POST customer.api/payments/lookup GET customer.api/orders/ORD123
Setu returns a structured business result, plus a natural-language reply if you want one.
"Aapka payment successful hai. Missing order ke liye humne ek support request bana di hai."
Languages with strong expected performance: French, German, Spanish, Portuguese, Italian, Dutch, Polish, Czech, Danish, Finnish, Greek, Norwegian, Romanian, Swedish, Croatian, Serbian, Ukrainian, Catalan, Breton, Arabic, Farsi, Hebrew, Turkish, Urdu, Hindi, Bengali, Gujarati, Kannada, Marathi, Nepali, Punjabi, Tamil, Telugu, Indonesian, Lao, Malaysian, Tagalog, Thai, Vietnamese, Chinese, Japanese, Korean, and Russian. Setu examples also include English and Hinglish.
Performance varies by model, and the list is not exhaustive. Hinglish is code-mixed; validate it with the specific model you deploy.
Setu turns language into controlled business execution. Your intents, your workflows, your APIs. Setu is the connective layer that makes them addressable in natural language.
A customer types a common problem in Hinglish. Watch Setu classify, extract, resolve the workflow, decide the outcome, and reply.
"Bhai mera paisa kat gaya but order nahi bana."
"Your payment was successful. We've created a support request to resolve the missing order."
request_id: req_9f4e · latency: 1.8s · reviewed by rules ✓
{
"intent": "payment_status",
"workflow": "payment_reconciliation",
"actions_taken": [
"check_payment",
"check_order",
"create_support_ticket"
],
"outcome": "ticket_created",
"ticket_id": "TKT-4820"
}Your workflows remain deterministic. AI understands the request. Setu validates the inputs and executes the workflow you declared, step by step.
Workflows are declarative. Version them. Diff them. Roll them back. AI never improvises past what your workflow allows.
workflow:
id: refund_status
trigger:
intent: refund_status
inputs:
required:
- order_id
steps:
- action: get_order
- action: get_payment
- action: get_refund_status
- condition:
if: refund.status == "pending"
then:
response:
template: refund_pending
else:
response:
template: refund_completed
response:
schema:
order_id: string
refund_status: enum
eta_days: integerSetu works with the backend you already trust. You don't need to rebuild your business logic. Map each semantic action Setu emits to an endpoint on your CRM, ERP, or commerce stack.
No rip-and-replace. No new database. Your backend keeps owning the truth; Setu keeps owning the conversation.
Setu is designed for teams that ship. The underlying model is replaceable. What you build on stays stable.
AI understands the request. Your business logic decides what happens.
Integrate Setu into your existing applications through clean HTTP APIs.
Return predictable intent and entity schemas your services can rely on.
Validate inputs, arguments, and actions before Setu ever calls your APIs.
Protect high-impact business actions with role checks and human confirmation.
Trace every request: intent → workflow → action → API → result.
Route cases to human agents when automation should stop. Cleanly.
Examples cover English, Hindi, Hinglish, and additional languages. See the full list in the How Setu works section.
The model powering understanding is an implementation detail. Your integration contract does not change when we upgrade it.
A small API surface, versioned end-to-end. You should be able to read the reference and know exactly what Setu will do.
Text in. Intent + entities out. Use when your app owns orchestration.
Text in. Full workflow execution, action calls, response out.
Your backend hands back the result of an action Setu asked it to perform.
import Setu from "@setu/sdk";
const setu = new Setu({ apiKey: process.env.SETU_KEY });
const result = await setu.execute({
message: "Bhai ORD123 ka refund kab aayega?",
session_id: "sess_123",
});
// {
// request_id: "req_123",
// intent: "refund_status",
// entities: { order_id: "ORD123" },
// workflow: "refund_status",
// status: "completed"
// }From zero to a live API call in under 10 minutes.
Bearer tokens, tenant IDs, key rotation.
Classify intents and extract entities.
End-to-end workflow execution.
Define, secure, and version the actions Setu can call.
Playbook schema, control flow, testing.
When to hold state with us, when to hold it yourself.
Async events for long-running workflows.
Predictable, versioned, retry-safe.
Official clients for Node, Python, Go.
Full OpenAPI spec, request/response schemas.
Quotas, retry-after headers, and fair-use policies.
Get an API key. Point it at your workflows. We host, scale, and meter. Fastest path from signup to a live API call.
An infrastructure module plus a container image. Setu runs inside your VPC on any major cloud. Customer data never leaves your network.
Bare-metal install with a 4–8 week onboarding. Fully offline. Same API surface, same workflow contract, zero external calls.
Every real conversation flowing through Setu leaves a trace. Missing intents, unseen entity values, workflow gaps. Adaptive workflows propose versioned diffs you can review, test, and merge, one intent at a time. The API contract does not change. Your workflows just get sharper.
intents: + - id: partial_payment + triggers: ["half paid", "partial", + "aadha paisa"] + entities: + - order_id + - paid_amount - id: payment_status
Setu is for engineering and product teams who already run their business on APIs and want a controlled way to expose that business surface to natural-language conversations. WhatsApp, voice, chat, agent copilots, internal tools.
The pattern fits anywhere a request needs to be understood, validated, and executed against an existing system: e-commerce support, fintech operations, citizen services, healthcare intake, logistics, EdTech desks.
Get an API key. Ship your first workflow this week. Talk to the Setu team about production rollouts and custom integrations.
One reply from a human within 24 hours. No spam.