Your catalogue, payments, messages, marketing and data, plus hundreds more apps through Composio and any MCP server. Each one is governed the same way.
Illustration of a connector under review, not a product capture.
Every name here has working code on the Nagent platform that Ateliq runs on.
Catalogue, orders, pay links, accounts and deliveries.
Shopify
Razorpay
StripeProduct and stock feeds read on a schedule or pushed to us. They only read.
Read for trends and results. Ateliq's agents draft; they don't post on their own.
Opt-in follow-ups, team chat and approvals where your team already works.
WhatsApp Business
OutlookThe stylist's voice, the operator's voice, and avatars.
Each agent can use the model that suits its job, or your own.
What the market lists, at what price, and what people say.
How people find you, in search and in AI answers.
Documents to learn from, media to work with, calendars to book.
Google CalendarCRM, service and integration platforms, read and written through governed connectors.
When the tool you need isn't on this page.
Shopify
WooCommerce
Adobe Commerce
SAP S/4HANA
UnicommerceSome tools need a plan that includes connectors. Each connection starts off until you turn it on.
Connecting is the easy part. What matters is what an agent may do once it is connected, and what you can prove afterwards.
Any connector action that changes something starts locked: a person approves it each time until an admin confirms that action. Ateliq's agents work at Assist, so their writes always wait for a tap.
An action can need up to three approvers, or only above an amount you set. The person who asked never counts as one.
Every call is logged in a chain where each entry seals the one before it. The export is signed, so anyone can check it.
Each workspace has a call limit. Reads retry up to three times. A write runs once, with a key that stops a repeat being applied twice.
Agents never see a password or key: an admin adds it on the review screen. Reminders say when a key is due to change, and old webhook secrets keep working while you swap them.
Requests can be signed, use OAuth, or present a client certificate (mutual TLS) for ERPs and banks that ask for one.
Each connector reaches only the hosts and actions it declares, never a private address. Fixed outbound addresses can be set, so your firewall can allow them.
Calls, errors and response times for the last seven days, per connector. One switch stops every call at once.
Marketplace, web and data calls, such as Oxylabs, ContactOut and DataForSEO, count in credits against each agent's daily and monthly cap.
Phone numbers, emails, card and account numbers can be replaced with tokens before a model sees them, and only go back to the system they came from.
A relay reaches systems inside your network over an outbound connection only, and database reads through it are read only.
Three flows, step by step, as they work in Ateliq.
Live today
Your Shopify catalogue, on the mirror and the counter.
Live today
The screen never takes payment. The shopper's phone does.
Live today
What your competitors list, and at what price, every Monday.
Give Orvane your system's API spec, or describe what it should read. It drafts a connector for an admin to approve.
The admin confirms each action and adds the key. Reads can then run; any write stays locked until a person approves it.
More of what Orvane buildsCan the Retail Analyst read yesterday's sales from our POS? It has a REST API.
Shopify and Razorpay are already connected, and your stock file comes in over SFTP. For the POS, send me its API spec and I'll draft a connector.
Approve.
Sent for review. When an admin confirms the actions and adds the key, I'll run one test read and show you the result.
Illustrative conversation. The brand and stores are fictional; it does not call a live AI.
Tell us what you run. We'll show you how Ateliq connects to it on a 20-minute walkthrough, or you can pre-order as a design partner.
No payment on the form. We reply within two working days. Or write to pb@ateliq.co.