Connecting to Agentify
Agentify lists your products in a catalogue that AI agents read and buy from. Your shop and your prices stay as they are, and Agentify keeps 0.1% of each sale.
Who buys here
Agentify publishes your products in its own catalogue, which AI agents read and buy from; an agent that buys starts at https://agentify.ad/llms.txt, which names the catalogue. Catalogues run by other people may list them too, and nothing guarantees that, and how many agents read Agentify's catalogue today is not something we can tell you yet. An agent is a program that a person handed a task and a budget; to finish the task it finds the goods it needs, pays for them and takes delivery, all by itself.
For you that is one more place to sell. Your range does not have to change, the prices stay yours, and your shop goes on working the way it works now. One thing is different: on the other side of the sale, in place of a person who opened your site and pressed the buttons, there is a program. It does not look at pictures and does not read reviews. It decides whether to buy from your product's description in the catalogue, so how precisely that text says what the buyer gets settles how many sales you end up sorting out by hand.
Buyers pay in USDC, a digital dollar, on the Base network, into a smart contract made for your crypto wallet, which then pays your share into that wallet. Turning USDC into money in a bank account happens outside Agentify.
Who is who
| Who | What they do in a sale |
|---|---|
| The buyer's agent | a program acting for a person: it reads the catalogue, decides from the product's description, pays and takes the goods |
| Agentify | publishes your products, asks the buyer for the payment, carries the paid order to you and your goods back to the buyer, and never holds the money |
| The facilitator | the payment service that checks the buyer's signed payment and executes it, into your payout contract |
| Your process, or your WooCommerce shop | your code, running beside your own systems, or your shop connected in the dashboard: it takes the paid order and delivers the goods |
| Your payout contract and your wallet | the contract receives every payment in full and pays it out, 99.9% to your wallet and 0.1% to us |
Agentify is in its pilot: it runs with its first merchants while the rules that are not settled yet get settled, and a few rules on these pages hold only until then, each saying so. There is no end date for the pilot yet.
What it costs and where the money goes
The buyer pays the price of your product into your payout contract, which keeps the money until it is paid out and then sends 99.9% to your wallet and 0.1% to us. Nobody, Agentify included, can change whom it pays. Our 0.1% is inside your price, and there is no subscription and no monthly fee. Your share reaches your wallet when you send a payout from your dashboard, at any time, and ours reaches us in the same transaction. If you send none, our own payout of every contract pays out yours too, on no fixed day. Money draws the whole path and says what you risk on the way.
When your buyer is charged
When the money moves depends on what you sell, and you choose it product by product:
| Your product | When the buyer pays | If you cannot deliver |
|---|---|---|
| Handed over at once by your system: a key, a link, access | after you have delivered, as the last step of the purchase | the purchase does not happen and the buyer pays nothing |
| Takes longer to prepare: a profile to set up, a supplier to ask | at the moment of purchase, before you deliver | the paid order is recorded as unfulfilled: you deliver late or close it, and any refund is yours to arrange |
| A parcel a carrier takes | at the moment of purchase, before you ship | as above: you ship late or close the order, and any refund is yours to arrange |
A WooCommerce shop's products are all charged at the moment of purchase, and the choice is not yours there: the connector publishes a download as a product that takes longer to prepare and a physical product as a parcel.
The same choices, with the words your engineer's code uses for them, are on Orders and fulfillment modes.
What the dashboard asks for
You connect on your own, in the dashboard, and it asks for four things:
- Your email address, where it sends a one-time sign-in link, or your Google account.
- The seller name buyers see beside your products and in the payment they approve.
- The address of your wallet on Base, where your share of every sale arrives; nothing of yours sits in an account of ours.
- How the goods are delivered: an API key you issue for your engineer's code, or your WooCommerce shop's address, as the next section says.
Your integration then publishes what you sell to the catalogue, each product with its title, description, price and list of what has to be given at purchase. That is the whole of what an agent reads.
Whether your product survives being delivered twice is yours to decide before connecting, since nothing in the dashboard asks it. The same order can reach you twice, and access, a key or a link go out a second time without loss, while a unit off a shelf does not. During the pilot we take on goods of the first kind only, because how money goes back to a buyer is not settled yet (Money). A parcel is the one exception, which Agentify has chosen to make: the buyer pays before you ship, and if it does not arrive, any refund is yours to arrange.
Your code or your WooCommerce shop
| Your code | Your WooCommerce shop | |
|---|---|---|
| Who builds it | your engineer, with the Agentify SDK, following The first test sale | nobody: the dashboard connects the shop and imports its products |
| What it sells | anything your systems can deliver | downloads and parcels from the shop (what can be imported) |
| Where it sells | the test channel, then the live one | the test channel, then the live one |
You sell through one of the two at a time. A third way, an order sent to you as a message that you confirm by hand before the buyer pays, is not available.
After you are connected
Who keeps your products up to date
Your integration does: when a product, its contents or its price changes, your code or the shop's import publishes it again.
What the dashboard shows
The dashboard is a page on our side that you sign in to with a link sent to your email. It shows your products, your orders and the receipts for the sales that went through. Signing in there is not the key your code sends us, so ending someone's session does not touch your integration.
How you stop selling
You can stop the sales yourself at any moment, with a pause on each product or one button that stops selling altogether. A paused product stops selling and disappears from the catalogue, while the orders already taken play out in the ordinary way. Leaving altogether is not available yet: pausing and revoking keys end no order already taken and delete no account, and the FAQ says what you can do instead.
What nobody watches for you
Nobody at Agentify watches your orders for you, so keep an eye on them and pause selling when your integration cannot deliver. Selling does stop on its own while your code is silent: while no process of yours has polled for ten minutes, your products leave the catalogue and every purchase is refused, and both come back at the next poll (What can go wrong).
Short answers — what this costs, what happens about refunds, who settles a dispute — are in the common questions.
How to start
The test environment is a place to practice your integration and make your own
test purchases. Buyers pay in test USDC on Base Sepolia. Live sales use real
USDC on Base and a separate account at https://agentify.ad; nothing is
copied between the two accounts. If you connect your real WooCommerce shop
in the test environment, its orders are test orders: do not ship them.
- Open the test dashboard, enter your email address, open the link in the message and press the confirmation button. Products asks how you want to add your products.
- On Products, choose how to add your products. With code shows the package, API key and quickstart; WooCommerce opens the shop connection (how it works).
- After your code connects, or your shop's check finds ready products, Products asks for your seller name and wallet in one form. Save them, then publish from your code or press Publish for the checked shop products. In the test environment the wallet only receives test USDC. Money explains how to get one.
- Make your first test purchase yourself, buying your own product with test USDC, as the guide's sixth step shows.
- For live sales, sign in to your separate dashboard at
https://agentify.adand connect your code or shop there. When your code connects or your shop's check finds ready products, enter your seller name and press Ask for live sales on Products. A wallet is not needed to ask; you can add it while you wait. Products keeps the request and any decision note, and an email tells you if the request is declined. After approval, save a wallet for real USDC before publishing. Your code publishes with a live key; a shop publishes its checked products from its live connection. Replacing a saved wallet on the live account takes forty-eight hours (why).
What changes between the two channels:
| Test environment | Live sales | |
|---|---|---|
| Address | https://test.agentify.ad |
https://agentify.ad |
| Account | sign in at its dashboard | a separate account: sign in again at its dashboard |
| Seller name | needed before the first product | needed again |
| Wallet | receives test USDC on Base Sepolia, which is worth nothing; a replacement applies at once | receives real USDC on Base; replacing a saved one takes forty-eight hours |
| API key | starts with csk_test_ |
starts with csk_live_ |
| Your first purchase | you make it yourself, with test USDC | — |
| Agentify's operator | not involved | approves your business before anything sells; ask on Products |
| Products | published with a test key | published again with a live key; nothing is copied |
| WooCommerce | available | available: the shop is connected again under the live account |
What is not settled yet
- Reconciling the money. Orders are visible in the dashboard, but a receipt is written at the moment the goods are delivered, so an order that is paid for and not yet delivered appears among the orders and not among the receipts. The money reaches your wallet one payout at a time, each covering every sale since the payout before it, and putting the two together is still yours to do.
- What happens when a purchased period runs out: renewing a subscription and buying the same access again are not designed yet.
- What we promise you when it is our side that goes quiet.
- Stopping your selling without being asked when your side answers too often that the goods are gone. Nothing does it today, so the switch is the one in your hands.
- When the pilot ends.