Product Hunt
सेतु·API-first · v1 shipping

Building for
Autonomous AI.

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

User message
→
Setu API
→
Intent + entities
→
Workflow
→
Your APIs
→
Business result
Try Setu

Pick a message.
Watch it become a workflow.

See customer requests rotate across Hinglish, English, Bengali, Tamil, Marathi, Gujarati, Spanish, and French. Pick a sample and run the demo workflow.

Multilingual examples
Hinglish
Bhai mera paisa kat gaya, par order nahi bana. Ref PYM-7021
Setu API
setu.api
$ setu.api ready
# hit Run understand + execute to send the message
>
The core message

AI understands.
Your systems execute.
Setu orchestrates.

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.

01User speaks naturally.02Setu understands the intent.03Setu extracts the required information.04Setu resolves the correct workflow.05Setu validates the action.06Your existing APIs execute it.07Setu returns the verified result.

It is not an autonomous agent. It is not a generic chatbot. It is API-first infrastructure for turning conversations into controlled business execution.

How Setu works

From conversation
to verified action.

Every request follows the same six-step path. Deterministic where it matters, language-aware where it counts.

  1. 01Read the message

    Understand

    Setu accepts raw customer messages in English, Hindi, Hinglish, and the multilingual languages listed below.

    Hinglish example
    "Payment ho gaya but order nahi bana"
  2. 02Classify the intent

    Identify

    Setu classifies against the intents you have declared in your workflow.

    payment_status
  3. 03Pull structured entities

    Extract

    Setu extracts the entities required by that workflow.

    payment_reference
    order_id
  4. 04Follow the declared steps

    Run workflow

    Setu walks the declared workflow: fetch inputs, evaluate conditions, choose actions.

    check_payment → check_order → reconcile
  5. 05Call your APIs

    Execute

    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
  6. 06Return a verified result

    Result

    Setu returns a structured business result, plus a natural-language reply if you want one.

    Hinglish example
    "Aapka payment successful hai. Missing order ke liye humne ek support request bana di hai."

Languages

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 real Setu trace

One message.
One traced execution.

A customer types a common problem in Hinglish. Watch Setu classify, extract, resolve the workflow, decide the outcome, and reply.

Customer · WhatsAppHinglish example

"Bhai mera paisa kat gaya but order nahi bana."

Setu → your customer

"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 ✓

execution traceSetu API
  • intentpayment_status
  • entitiespayment_reference · order_id
  • workflowpayment_reconciliation
  • actionscheck_payment, check_order
  • decisionPayment successful · order missing
  • actioncreate_support_ticket
// structured business response
{
  "intent": "payment_status",
  "workflow": "payment_reconciliation",
  "actions_taken": [
    "check_payment",
    "check_order",
    "create_support_ticket"
  ],
  "outcome": "ticket_created",
  "ticket_id": "TKT-4820"
}
Workflow engine

Define your business logic.
Let Setu handle the conversation.

Your workflows remain deterministic. AI understands the request. Setu validates the inputs and executes the workflow you declared, step by step.

  • triggerWhich intent kicks the workflow off.
  • inputsRequired and optional entities, with validation.
  • stepsOrdered actions, each mapped to one of your APIs.
  • conditionsBranching decisions based on prior step results.
  • responseStructured business response and reply template.

Workflows are declarative. Version them. Diff them. Roll them back. AI never improvises past what your workflow allows.

refund_status.workflow.playbookv3 · deterministic
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: integer
Existing systems

Keep your
existing systems.

Setu 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.

01
Setu
intent + entities
02
Semantic actions
get_order · get_payment
03
Your APIs
CRM · ERP · commerce
04
Business result
verified · logged
semantic action mapcustomer-defined · versioned
get_order_statusOMS
GET /orders/{id}
get_payment_statusPayments
POST /payments/lookup
create_support_ticketCRM
POST /tickets
trigger_reshipmentCommerce
POST /orders/{id}/reship
get_refund_statusPayments
GET /refunds/{id}
update_customer_profileCRM
PATCH /customers/{id}

No rip-and-replace. No new database. Your backend keeps owning the truth; Setu keeps owning the conversation.

Why Setu

Infrastructure primitives,
not AI marketing.

Setu is designed for teams that ship. The underlying model is replaceable. What you build on stays stable.

workflow.playbook

Deterministic workflows

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

REST · JSON

API-first

Integrate Setu into your existing applications through clean HTTP APIs.

schema-locked

Structured outputs

Return predictable intent and entity schemas your services can rely on.

input · action

Validation & guardrails

Validate inputs, arguments, and actions before Setu ever calls your APIs.

RBAC · 2-step

Permissions & confirmation

Protect high-impact business actions with role checks and human confirmation.

traces · logs

Observability

Trace every request: intent → workflow → action → API → result.

handoff

Human escalation

Route cases to human agents when automation should stop. Cleanly.

language

Multilingual by default

Examples cover English, Hindi, Hinglish, and additional languages. See the full list in the How Setu works section.

model-agnostic

Replaceable model layer

The model powering understanding is an implementation detail. Your integration contract does not change when we upgrade it.

For developers

One small API.
Predictable schemas.

A small API surface, versioned end-to-end. You should be able to read the reference and know exactly what Setu will do.

Understand

Text in. Intent + entities out. Use when your app owns orchestration.

Execute

Text in. Full workflow execution, action calls, response out.

Action results

Your backend hands back the result of an action Setu asked it to perform.

quickstart.js
Hinglish exampleNode · @setu/sdk
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"
// }
Coming next
  • Sessions
    Multi-turn session state, if you want us to hold it.
  • Workflows
    Manage workflows programmatically. Versioning included.
  • Intents
    Manage the intent catalog outside of workflow files.
  • Webhooks
    Subscribe to events across the lifecycle of a request.
Quickstart→

From zero to a live API call in under 10 minutes.

Authentication→

Bearer tokens, tenant IDs, key rotation.

Understand→

Classify intents and extract entities.

Execute→

End-to-end workflow execution.

Actions→

Define, secure, and version the actions Setu can call.

Workflows→

Playbook schema, control flow, testing.

Sessions→

When to hold state with us, when to hold it yourself.

Webhooks→

Async events for long-running workflows.

Error codes→

Predictable, versioned, retry-safe.

SDKs→

Official clients for Node, Python, Go.

API reference→

Full OpenAPI spec, request/response schemas.

Rate limits→

Quotas, retry-after headers, and fair-use policies.

Deployment

Three ways to run it.
Same API surface underneath.

AStartup · SMB

Managed SaaS

Get an API key. Point it at your workflows. We host, scale, and meter. Fastest path from signup to a live API call.

Serverless GPU · high-throughput inference
BMid-market

Bring Your Own Cloud

An infrastructure module plus a container image. Setu runs inside your VPC on any major cloud. Customer data never leaves your network.

BYOC · VPC-native · telemetry only
CEnterprise · BFSI · Gov

On-prem · Air-gapped

Bare-metal install with a 4–8 week onboarding. Fully offline. Same API surface, same workflow contract, zero external calls.

Compliance-first · $50k+ setup
Coming soon

Workflows that
write themselves.

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.

// proposed by setu
Hinglish trigger example
diff · payment_reconciliation.playbook
  intents:
+   - id: partial_payment
+     triggers: ["half paid", "partial",
+                 "aadha paisa"]
+     entities:
+       - order_id
+       - paid_amount
    - id: payment_status
observed in38 requests · last 7 days
Who it's for

For teams with APIs
and a language problem.

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.

D2C fashion, beauty, groceries
Fintech customer support
Government citizen services
Healthcare intake & triage
Logistics operations
EdTech support desks
Internal agent copilots
Voice IVR modernization
Early access · Q1 2027

Turn conversations
into verified actions.

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.