Data integration for AI coding: ship data-heavy apps with your agent
Your agent can write the app. It can't guess your data.
Developers, agencies and in-house teams use dcupl to build catalogs, customer portals and order entry on ERP and product data. Your coding agent builds on the real model of that data, and the frontend can start before the backend is finished.
The CLI is free on npm and runs locally. The Console has a free tier.
In production at industrial companies since 2022, from steel to eyewear.
The problem
Agents don't crash on bad data. They succeed on the wrong data.
Guessing
The agent invents a field name, gets an empty array back and reports success.
Control
Changes land faster than anyone can review them. Nothing says what is pending.
Time
And the rollout deadline still looms next month.
Nothing crashed. Nothing is right.
Why we build dcupl
The hard part of an app was never the code. It's the data.
Agents made code cheap. So the data path now decides whether an app is right. We believe every team building with agents deserves data its agent can read, check and trust before anything ships.
How we do it
Give the agent the data, not a guess.
Read the real model first
The agent asks for actual fields and types before it writes a filter. Wrong names fail loudly, not silently.
Answer in JSON
With --json each command returns structured output. The agent knows what happened, and so do you.
Nothing live without a build
Changes are staged, workflows run on a dev runner first. A person approves what goes live.
The difference in one session. Same prompt, same data.
You, to both agents: import new-prices.csv and list products on sale under €50
Import complete. No products are on sale under €50.
The same guess, sent to the dcupl CLI
$ dcuplappqueryexecute--model Product \--query'[{"attribute":"on_sale","operator":"eq","value":true},{"attribute":"price_eur","operator":"lt","value":50}]' \--json{"success":false,"error":"Attribute \"on_sale\" not found on model \"Product\". Did you mean \"onSale\"?","code":"ATTRIBUTE_NOT_FOUND"}
Exit code 1. The guess stops here, with the right name in the error.
Reported as done. The answer is wrong. The prices in products.json are already overwritten, and nothing failed, so nobody looks.
The right 9 products, from the built data. The 5 new prices went live with the build, not before.
The commands and the CLI's replies were captured on twelve demo products; … marks a cut. The agent's lines and the session without dcupl are illustrative.
A salesperson asks the catalog in plain language while the customer waits. What Claude looked up and answered, and what is behind it: the same catalog data, one connection, read-only.
Three CSV exports, one data model, a catalog page with facets, counts and a price filter. The story for the business side first, then the build step by step, with the code behind every screenshot.
The CLI stages before it builds. A workflow variant runs on a dev runner before it is promoted. An API instance serves the old data until the update is done. One rule, three places, and why it matters when agents write the changes.