dulyx.

AI agents inside the system you already use

Your data deserves
a conversation.

Ask the way you talk. dulyx queries the ERP, CRM or API your company already has, answers with live data and only writes anything after your yes.

  • Duly assistant
  • Léo finance
  • Sofia support
  • Íris logistics
a working day, with and without dulyxscroll and the clock moves
07:59

scheduled workflow

The summary is already in.

Nobody has opened the ERP yet. A workflow ran at the set time, pulled the stalled orders and sent the summary to the manager's WhatsApp, before the meeting.

illustrative scenario · numbers from the demo ERP

  1. 1Triggerevery day · 08:00
  2. 2Search Ordersstatus = under review
  3. 3Conditionany stalled?
  4. 4Notifymanager's WhatsApp
Monday, August 3107:59
Duly · dulyxGood morning. 4 orders under review, R$ 123.00 in total…
Dulycompany number
today

Good morning. 4 orders under review, R$ 123.00 in total. The oldest is from 07/20, stalled for 43 days. Want me to release any of them?

scheduled · every day at 08:00

I'll check in the meeting, thanks

08:12

the usual way

Without AI, four steps.

To find the latest order under review: open the ERP, filter, sort and open the order. Every day, for every question, by whoever knows where to click.

real turn · demo ERP

01open the ERPsales › orders
02filter by statusstatus = under review
03sort by datedate ↓ newest
04open the orderthe first one on the list

and again tomorrow, for every question

Ask your way
09:04

Renata · sales representative

Which customer stopped buying?

39 customers in Belo Horizonte. To find who stopped, she would export 2,649 orders and compare dates, customer by customer. Over an hour, and whoever stopped would slip by unnoticed.

illustrative scenario · customers from the demo ERP

portfolio · Renata · Belo Horizonte/MG
39customers
today's way · spreadsheet
  1. 1export the 2026 orders2,649 orders
  2. 2filter the city: Belo Horizonte39 customers
  3. 3sort by customerA → Z
  4. 4compare dates, one by one0/39

whoever stopped shows up in no report

which BH customers haven't bought in 45 days or more?

DulyList orders · List customers

17 of the 39 BH customers have gone 45 days or more without buying.

  • Olívia Gomes #271last purchase 04/15 · 3 orders this year138 days
  • Wagner Klein #26810 orders this year · R$ 18,989.3272 days
  • Lucas Junqueira #68 orders this year · R$ 17,875.8363 days
10:30

on your company site

What does Dulyx actually do?

It puts an agent inside your system, through the API it already has.

Price, stock, lead time, orders: the agent answers with what your ERP knows right now and acts directly at the source. On your website, on WhatsApp or inside the assistant your team already uses.
yourcompany.com
Dulyqueries and acts in your system

Hi! I can check price, stock and delivery times, and handle orders right here.

do you have 2kg brown rice?

We do, $6.20. Want me to add it to your cart?

add 2 please

Add Item to Cart
Brown Rice 2kg · id 5Quantity 2Total $12.40
ConfirmNot now
confirmed by you

Done. Your cart has 2 × Brown Rice 2kg, total $12.40.

cart · updateditem Brown Rice 2kgquantity 2total $12.40
Ask anything…
Website widgetsix scenarios · one platform
11:40

on the company WhatsApp

Does it work on WhatsApp?

The same agent, on your company’s number.

Connect your own number through Meta’s Embedded Signup and choose who answers on each one. You ask in the chat and the reminder arrives on your WhatsApp: “remind me tomorrow at 9am” or “every day at 8am send me the open orders”. If someone on your team replies, the agent goes quiet for as long as you set.
08:00
Sofia · Supportbusiness account
today

send me the open orders every day at 8am

Got it: every day at 08:00, on this number. Since it’s recurring, can you confirm?

yes

scheduled · every day at 08:00tomorrow

3 open orders. #45892 Carter, 2 days ago · #45901 Bennett, today · #45907 Foster, today. Want me to release any?

Message
  • asked in chat

    scheduled every day at 08:00, next send tomorrow

  • outside 24 h

    Meta-approved template · R$ 0.035 per message

  • a teammate replied

    the agent goes quiet in that chat for 30 min

official integration

WhatsApp Business Platform, through Meta’s official API.

Embedded Signup on your company’s number. No virtual number, no third-party app and none of the bans that take down unofficial automation.

Replying to whoever wrote in
R$ 0within the 24 h conversation window
Message outside the conversation
R$ 0.035per delivered message · billed by Meta to your account, Brazil rate
Dulyx markup
R$ 0just the agent’s credits, when it replies
13:00

in Claude, ChatGPT or Cursor

Who calls my API?

Dulyx does.
The model doesn’t.

On the AI side, only questions and answers in text. Credentials, URLs and requests stay on the Dulyx side. Works with Claude, ChatGPT, Cursor and anything else that speaks MCP.
Claude dulyx · MCP connector

what’s the latest order under review?

dulyx · Search Ordersstatus = under review

It’s order #5996, from Úrsula Oliveira (Porto Alegre/RS), placed on 08/30/2026, totaling R$ 1,250.96.

release it

dulyx · Change Order Statusproposal created · nothing written

Before writing: order #5996 goes from A (under review) to L (released). Confirm?

yes

dulyx · confirm_changewritten to the ERP

Done, #5996 is released.

Reply to Claude
illustrative conversation · demo ERP
  • Reaches the model

    The question, the agent’s instructions and the slice of data that survived the cut.

  • Never reaches it

    URLs, credentials, database access and anything not enabled in the context.

  • the same connector

    Works the same in ChatGPT, Cursor and any client that speaks MCP.

your team’s assistant
ClaudeChatGPTCursor
and anything else that speaks MCP
questions and answers, in text
no URL, no credentials
dulyxresolves the context, fetches and filtersfunnel applied
credentials, URL and request
this side only
your system
ERPCRMAPI
out of the model’s reach
MCP bridgecredentials never cross over
14:10

on the team board

Does it organize the team’s work?

Boards the agent reads, creates and moves from the chat.

Boards, lists and cards, linked to the agent’s knowledge base. “What’s overdue?” becomes an answer; “create a card due Friday” becomes a card with a due date and an owner. Attachments, checklists and comments live on the card, and archiving asks for confirmation.
board · Saleslinked to context GESTAO_PEDIDOS

To do3

Call the supplier about batch 2210
Fridayyouby the agent
Check the invoice for order #45892
Thursdaychecklist 1/3
Update the shipping rates for the South region
Monday

Doing2

Packaging quote for order #45901
todaychecklist 2/4
Answer ticket 1187 from Bennett
yesterdayby the agent

Done2cards here count as done

Reissue invoice 1187
doneby the agent
Release order #45880
done
you

create a card to call the supplier by friday

duly

Created in To do, due Friday, owner you. I attached the quote that was in the conversation.

15:00

where the data goes

The model asks. dulyx executes.

On the AI side, only question and answer in text. Credentials, URL and request stay on the dulyx side, and a cheap model cuts what the expensive model doesn't need to see. What isn't sent isn't billed.

real turn · demo ERP

who thinksAI modelClaude, ChatGPT, Cursor…
question and answer, in text
who executesdulyx.credentials, URL and request
through the API you already have
where data livesYour ERPout of the model's reach
a real turn · records
5,939
read in your ERP
0credentials, URLs or requests in the model's hands
turn #4812 · data used
  1. Context resolvedGESTAO_PEDIDOS16 ms
  2. GET /api/pedidos?status=Athe caller was dulyx200
  3. Tax IDs (CPF, CNPJ)masked before going upok
  4. Data cut5,939 read → 564 sent−90.5%
  5. PUT /api/pedidos/5996confirmed by you200
  6. Verificationa second model checked the answerok
exports to CSV, Excel and PDF
16:30

before the end-of-day meeting

Can it put together reports?

Pages, PDFs and spreadsheets, with live data.

A report queries your integrations’ actions and builds the document: title, figures, table and chart, on the page size you choose. Generate it on the spot with the parameters you fill in, or ask AI to draft it from the conversation.
report · open ordersA4 · portrait · generated now

Open orders · September 2026

47orders
$184,320outstanding
$3,921average order
ordercustomeramountdays
#45892Carter$12,4802
#45901Bennett$3,9200
#45907Foster$8,1500
#45880Sloan$1,2755
orders per week
wk 19
wk 216
wk 313
wk 49
4 sources · 2 pages · 3.1 creditsview online · PDF · print · spreadsheet
17:20

guided mode

What if it wants to change something?

Nothing is written without your yes.

The agent proposes the change and waits. No write runs until a person approves it, and the button lives in the workflow, not in an email.
Flow · Overdue ordersworkflow builder
yesnoTriggerStartIn chat · ordersActionFetch OrdersGET /pedidos?status=AConditionAny overdue?If due date < todayApprovalConfirmAwaits approvalActionUpdate StatusPUT /pedidos/statusDisplayDisplayTable in chat
running the workflow0/6 steps
Workflow with approvalamber = waiting on a person
Flow · Overdue orders
TriggerStartIn chat · ordersok
ActionFetch OrdersGET /pedidos?status=Aok
ConditionAny overdue?If due date < todayok
yes
ApprovalConfirmAwaits approvalwaiting for you

move 3 orders to collections

ApproveReject
ActionUpdate StatusPUT /pedidos/status
no
DisplayDisplayTable in chat
amber = waits for a person
17:50

and again tomorrow

And what does it do without me asking?

It runs on the schedule you set.

A workflow chains the actions you’ve already set up: it fetches, decides, repeats for each item and acts. Every day, on weekdays, once a month or every 15 minutes. Describe it in plain text and AI drafts it; a good conversation becomes a workflow with one command.
workflows · scheduledtime zone: your browser’s
  1. every day · 07:30
    Stalled orders4 steps · WhatsApp alert
    TriggerActionConditionAlertok · today 07:30
  2. Mon to Fri · 18:00
    Daily cash close6 steps · runs on its own
    TriggerActionLoopActionok · yesterday 18:00
  3. every 15 min
    Stock below minimum3 steps · WhatsApp alert
    TriggerActionConditionAlertskipped · API down
  4. day 1 · 09:00
    Overdue invoices this month3 steps · table in chat
    TriggerActionDisplaynext · day 1 · 09:00
  5. in chat
    Release order5 steps · asks for approval
    TriggerActionApprovalAction12 runs · last one today
every day · weekdays · once a month · every X minutes · just onceworkflows with approval can’t be scheduled: they wait for a person
18:00

who answered today

Not an assistant. A team.

Each agent is a role: a name, a way of answering and a clear limit on what it can see, do and spend. A platform rule, not a prompt.

  • Duly Assistant

    Answers about the data and documents you registered. Ready out of the box in a new account.

    readdocuments
  • Léo Finance

    Invoices, overdue bills and duplicate copies. Read-only: changes require a person.

    read only
  • Sofia Support

    Manuals, procedures and FAQ, in the site chat and on WhatsApp, with the same memory.

    readsite + WhatsApp
  • Íris Logistics

    Tracking and delivery changes. Every change goes through confirmation.

    write with confirmation

In the dashboard, on the company WhatsApp, in your site chat and in Claude, ChatGPT or Cursor, through MCP. The same agent, the same memory, the same limits.

end of the workdayinside: what holds the day together
#4812

the turn, step by step

How do I know what it did?

Every answer leaves a trail.

Step by step: what was looked up, what was cut and what was blocked, with the numbers already worked out. The report your legal team would ask for is a tab, not a project.
turn #4812 · agent “Duly · Sales” LIVE
Context resolved: GESTAO_PEDIDOS
3 available · 1 activated
16 ms
GET /api/pedidos?status=atrasado
called by Dulyx · the model never touches your API
ETag 304
Data cut
5,939 read in your ERP → 564 sent to the model
−90.5%
PUT /api/pedidos/45892
waiting for the user to confirm
on hold
limit used 18%cost 2.4 creditstime 1.9 ssource live ERP
4×4

security

What are the guardrails?

Mechanical limits, at every layer.

None of them depend on the model behaving. They are Dulyx rules, applied before data goes up, during the turn, before answering and on the channel. What the agent isn’t allowed to do, it has no way to do.
Before the model01
  • Credentials stay home

    URLs, keys and requests stay on the Dulyx side. The model gets the question, the agent’s instructions and the slice of data.

  • Tax IDs masked

    Brazilian CPF and CNPJ numbers are detected by value, in any field, and swapped before going up. The real number only returns when your system is called.

  • Data funnel

    A cheap model cuts what the expensive model doesn’t need to see. In a real turn: 5,939 read, 564 sent.

  • Scope per token and per agent

    Each token sees only the contexts enabled for it; each agent, only its own. The stricter of the two always wins.

During the turn02
  • Writes only with your yes

    The proposal shows what will change and where, then waits. It expires: a late yes doesn’t write.

  • Caps on rounds, calls and credits

    Per turn, including when consulting another agent. Mechanical: it doesn’t judge merit, it just counts.

  • Capped pagination

    At most 20 pages and 2,000 records per query. A source that repeats a page never turns into an endless loop.

  • Blocked destinations

    Internal or private addresses are never called, not even through a redirect.

Before answering03
  • Checked by a second model

    It checks the answer against the turn’s data before sending. That call is on Dulyx.

  • Moderation

    Insults, discrimination, threats and defamation never go out in your company’s name. Without a verdict, the answer doesn’t go out.

  • Credit caps at four levels

    Account, context, token and agent. Hit the cap and it blocks. Overage is never charged unless you buy it first.

  • A trail for every turn

    What was looked up, cut and blocked is recorded. The data used tab exports to CSV, Excel and PDF.

On the channel04
  • Human pause on WhatsApp

    If someone on your team replies from the app, the agent goes quiet in that conversation for as long as you set.

  • Number linked by code

    Before scheduling a reminder, the person confirms their own number with a code. Linking doesn’t open a turn or use credits.

  • Website chat only on your domains

    The public key only answers on allowed domains, with a cap per visitor. Anywhere else, it doesn’t answer.

  • Purge on a deadline

    Attachments, generated files and session logs are deleted from disk after the number of days you choose.

~91%

pricing

How much does it cost?

You only pay for what reaches the model.

Before anything reaches the expensive model, a cheap model cuts what it doesn’t need to see. What doesn’t go up doesn’t go on the bill. Plans and pricing are shared in early access.
From your ERP to the model
564 of 5,939 records
Read at the source5,939
After the first cut2,010
After the second cut960
Sent to the model564
A real turn5,939 read · 564 sent
Data held back~91%of the data read from your ERP never reaches the model
Handed to the model0credentials, URLs or requests in the model’s hands
To integrate1calland the agent is live, no AI team needed
15

the rest of the dashboard

What else does it do?

The rest of the dashboard, one line each.

Everything here already exists in the platform, on screen. None of it is a roadmap promise.
  • Memorylearning

    an answer approved in chat comes back the same · no new AI call

  • Knowledge basedocuments

    PDF, image, spreadsheet and web page · up to 20 MB · AI review

  • Environment mapoverview

    connected contexts, actions and sources · turns lighting up live

  • Agent modesbehavior

    with AI · decider, no model in the turn · guided by a script

  • Handoffteam

    one agent consults another · each within its own scope

  • Verificationquality

    a second model checks the answer before sending

  • Users and permissionsaccess

    per person and per agent · no code scattered around

  • Asker profileconversation

    language, tone and level of detail · sent with every message

  • Usage and creditsaccount

    balance, cost per conversation and response time · buy without leaving

  • Conversationshistory

    CSV, Excel and PDF · integration health · data used

  • Website chatchannel

    bubble, inline, React or standalone link · cap per visitor

  • API and streamingcode

    scoped token · SSE · cURL, Node, Python and C#

  • Files in the conversationattachments

    receives files · returns PDFs

  • Personal dataLGPD

    CPF and CNPJ masked before reaching the model

  • Model tiersmodels

    you pick the tier, not the model · switches on its own if one goes down

</>

technology

And what does it run on?

Only official APIs, under direct contracts.

No unofficial middlemen, no virtual numbers, no borrowed accounts. Dulyx is a direct customer of each provider, and your data only goes where the contract says. You choose the model tier; which API serves it is the platform’s call.
  • WhatsApp Business PlatformMeta

    official Cloud API · Embedded Signup on your number · approved message templates

  • OpenAI APImodels

    GPT family · direct contract with the official API

  • Claude APImodels

    Claude family, by Anthropic · direct contract with the official API

  • Gemini APImodels

    Gemini family, by Google · direct contract with the official API

0:57

on video

Can I see it in a minute?

In 57 seconds, a real turn in the demo ERP.

The question, the API lookup, the answer with the order items, and the write that only happens after your yes. Then where the data goes and who answers.
Read instead of watching
  1. “Qual o último pedido em análise?” (which is the latest order under review?). Without AI, it takes four steps to the ERP: open the ERP, filter by status, sort by date and open the order.
  2. Dulyx plugs into the other side of the ERP, through the API it already has, with the AI agents inside.
  3. A real turn in the demo ERP: “ult ped analise” (latest order under review) goes through Dulyx to the ERP and comes back with order #5996, from Úrsula Oliveira, R$ 1,250.96, and its four items. “liberar” (release) becomes a proposal to change the status from A to L, which waits in Dulyx and only reaches the ERP after Confirm — and stays in the log.
  4. The model asks, Dulyx executes: the credentials stay on its side, and of the 5,939 records read, 564 go up to the model.
  5. It is not an assistant, it is a team: Duly, Léo, Sofia and Íris come out of Dulyx, each with a role and a scope.
  6. Your data deserves a conversation. Waitlist open at dulyx.com.br.
Dulyx in 57 sreal turn · no audio · UI in Portuguese
4

getting started

Four steps. Once.

No AI team and no model to pick. The four steps at the start of the day were a routine; these you do once, and the agent is live.

  1. 01Create the contextthe subject and who can ask
  2. 02Connect your APIsthe one the system already has, or OpenAPI
  3. 03Set the permissionswhat each agent sees, does and spends
  4. 04Turn on the channelsdashboard, WhatsApp, site and MCP
?

Straight answers

What you might still want to ask:

  • Still have a question? .
DulyAssistant · Questions about Dulyx

Where does my data live?

In your system, where it always was. Dulyx queries your API on every question and only stores what you told it to: the documents you uploaded and the conversation log. Your data never trains a model.

  • Where does my data live?

    In your system, where it always was. Dulyx queries your API on every question and only stores what you told it to: the documents you uploaded and the conversation log. Your data never trains a model.

  • What about LGPD and privacy?

    Only what you enabled leaves your system, only the slice that’s needed reaches the model, and every access is logged: what went out, through which agent, for what and when. The report your legal team would ask for is the Data used tab, ready to export, not a separate project.

  • My system has no API. Can I still use it?

    You can start today: files, spreadsheets and web pages become a searchable base, without a single line of integration. Without an API, the agent answers about what you uploaded. To query live data and take actions you need an API, which usually comes from your ERP vendor.

  • Do I need a developer?

    To chat, no: the website chat, WhatsApp and AI assistants don’t need any code. To embed it in your software, yes, but not a new team: whoever already looks after your system can do it with the docs in hand, without learning anything about AI. And upkeep afterwards happens on screen, not in code.

  • What happens when the AI gets it wrong?

    Every answer comes with its source, every change stops for confirmation and, when it isn’t sure, the agent asks instead of making things up. Still got it wrong? The whole conversation is recorded: you find the step, fix the setup and the fix applies from the next answer on.

  • How much will I pay?

    In credits per conversation, with a per-agent limit you set. No per-user pricing and no surprises: the dashboard shows the cost of every answer. Plans and pricing are shared in early access.

  • What if I want to leave?

    Your data never stopped being yours: your system stays the same and revoking a key takes one click. Leaving Dulyx is pulling a plug, not migrating a database.

  • Still have a question? .
dulyx.

The conversation starts here.

Early access

AI in your operation shouldn’t cost a whole team.
It should fit in an afternoon, on one screen, on a bill you understand.
Be among the first to put agents inside your system.

DulyAssistant · Waitlist
7 quick questions · under 2 minutes

What’s your name?

What’s your name?

No spam. Just one note when Dulyx is available.