What it is, in one sentence
A service window on the catalogue you already run, answering six questions that any clerk would understand, and refusing everything else until you say otherwise.
/ agent readiness
The buying is moving to machines. Be readable when it arrives.
Buying software now asks for price, stock and lead time by itself, and it acts on whatever comes back. We make an industrial catalogue readable, answerable and auditable by those agents, inside your own infrastructure and without moving your data.
Check your own domain on the right. Twelve checks, three seconds, no account, nothing stored, no private address requested. The quote underneath is generated from your own scan.
mscdirect.com
fastenal.com
grainger.com
dxpe.com
this site
waiting for a domain
enter your address, or scan an example above
twelve checks, reported separately, with response codesalso as an API
15 of 22
do not answer a machine: 8 refuse, 4 serve a placeholder, 3 never reply
0 of 22
name an AI agent in robots.txt, or offer a way to query a catalogue
3.2 / 10
readiness of Hubbell (hubbell.com), an electrical manufacturer, audited 16 October 2026
/ in plain words
Software is starting to do the shopping
A buying assistant, not a person, is increasingly the one asking what you have, how many, how fast and how much. It asks your website the way one program asks another. If your site only answers people, the assistant moves on and you never hear the request you lost.
Nothing here needs a new system. Your catalogue and your prices stay where they are. What changes is that a machine can ask about them, under rules you set, and you receive the log of what was asked.
/ the whole thing in one picture
Four layers. Three belong to Google, OpenAI and Stripe.
Autonomous purchasing was standardised in four layers, and three of them are owned by the platforms. The first one, the layer that lets anyone ask your catalogue a question, is the only one that has to run inside your own systems. That is the layer this product builds.
/ in plain words
Layer one is the door
The door an assistant knocks on when it wants to know something about your catalogue. It is yours, and today it is closed.
/ in plain words
Layer two is the counter
How the order gets placed once the assistant has decided to buy. Google and OpenAI own this one.
/ in plain words
Layer three is the permission
Proof that a real buyer allowed the spend. Owned by the same platforms, handed to the standards bodies.
/ in plain words
Layer four is the change
The payment, counted in cents per question. Stripe and Coinbase own it and charge almost nothing.
Read the detail layer by layer, with owners and dates: the agent economy.
/ how it works
Four steps, and your data never leaves
The gateway is a reader, not a warehouse. It stands in front of the systems you already run and answers questions on their behalf, under rules you set, and every call is logged for you.
What it is not
Not a new ERP, not a data warehouse, not a marketplace, and not a place where your contract prices are copied. In the first month it does not even accept orders.
/ before and after
The same question, asked twice
Three questions a buying assistant asks, and what it gets from a typical distributor site today against what it gets once the gateway is in place.
/ where the industry stands
15 of 22 do not answer a machine
We requested twenty-two US industrial distributors as a program, not as a browser. Each bar is one check across all of them: green passes, amber partly answers, red refuses. The right column is the same thing in plain words.
The pattern is not random. The checks almost everyone passes are the free ones: a sitemap, and being allowed in at all. Every check that requires a decision about machines fails across the whole industry at once, which is why this is a decision problem rather than a technology problem. Every row, every response code: the evidence, raw data in field-run.json.
/ why now
Eighteen months, and a deadline already set
Every marker below is a standard that shipped, or a compliance date a regulator has already published. This is not a forecast.
/ what an agent asks
Three questions, and what most sites return
We sent the requests a procurement agent would send to seven distributor sites on 16 October 2026. This is what came back.
| What the agent asks | What most sites return | Cost to you |
|---|---|---|
| "Do you have 6205-2RS in stock" | A 404 from a script, or a page with no price and no stock | The agent recommends another supplier |
| "What does it cost for my account" | Nothing machine-readable: the price is rendered for a human only | You are compared on list price, not on your agreement |
| "Send the datasheet and the certificate" | No document endpoint exists, so the agent guesses from a description | Compliance risk lands on the buyer, and then on you |
Four of the seven refused the search path outright, one served a captcha, one returned a large page with no price anywhere in it, and one did not answer at all. None returned a price, a stock figure and a document together.
/ what we do
Measure it, serve it, sign it
Three products in sequence. The diagnostic exists so you never buy the gateway on faith, and the records exist so what an agent relays about you can be checked years later.
Step one
Diagnose
$2,500, credited
A live agent run against your public surface and, under NDA, your catalogue. You get the raw transcript: every request, every response code, every search that returned nothing.
- One domain, five working days
- Gaps listed by product line
- Credited against month one
Core product
Step two
Serve
$1,500/mo per catalogue
Six tools over the catalogue you already run, under your access rules, read-only for the first month, with every call logged and delivered to you.
- MCP and REST, in your VPC or ours
- Your prices, your rules, per buyer
- Every call logged
Step three
Prove
$500/mo per catalogue
Signed records for the facts that have to survive an audit, each with the basis of the claim stated separately and the evidence bound by its fingerprint.
- Ed25519 signatures, sha256 evidence
- Published keys, offline verification
- Revocable, never silently
/ what you are choosing between
Four routes, and only one makes the catalogue answer
The work is already being bought in three other forms. Comparing them honestly is more useful than another list of features, and it tells you what our floor price is competing with.
| Route | What it costs | What it actually changes | Does your catalogue answer? |
|---|---|---|---|
| Agency retainer, AI visibility | median $6,850 a month (First Page Sage, 1,146 quotes, Oct 2026) | They write content and try to get you mentioned in AI answers. Your catalogue still cannot be asked a question. | no |
| A visibility dashboard | a subscription, usually a few hundred a month | It shows where you appear. It changes nothing in your own systems. | no |
| Build it yourself | your developers, several months, then maintenance | Full control. You also own the mapping to conventions that keep moving. | partly |
| Connect.ARLI gateway | $1,500 to $4,500 a month, metered, from $8,000 to connect | Reads the catalogue where it lives and answers the six questions, under your rules, with every call logged. | yes |
The first two routes sell attention. The third sells control and costs you a year. The fourth is the only one that changes what a machine can get out of your catalogue, and it is priced below the first one. The longer comparison, in plain words: plain words.
/ what a year costs
Priced below the market, and shown in one picture
Market rates for this work are published, so we price against them rather than against our own ambitions. The median agency retainer buys attention; ours buys a catalogue that answers.
Verified by buyers, brokers and auditors: free, forever, without an account. Full price list and worked examples: pricing.
/ the questions a buyer asks
What happens to your data and your prices
Six answers that a procurement review asks for, in the order the questions usually arrive.
/ 01
Your data does not move
Read-only in the first month. The gateway answers from your systems and stores nothing about your catalogue contents.
/ 02
Your prices stay yours
Your rules decide who sees which price. No contract price is published. We never see the contents of a buyer agreement.
/ 03
The log is delivered to you
Every call, every refusal, every question that returned nothing, in your hands rather than in our dashboard.
/ 04
Revocation is one command
A catalogue, a record or an entire deployment can be withdrawn without a support ticket.
/ 05
It runs in your cloud or ours
Enterprise deployments run inside your environment, with SSO and your own audit trail.
/ 06
No SOC 2, and we say so
We are small and honest about it. Ask for the questionnaire and we fill it in before any commercial conversation.
Data flow, obligations and the cryptography behind the records: security.
/ what we will not tell you
Agent traffic is small today
You are not buying traffic from us and we do not promise any. What you are buying is the position, and the work that makes a catalogue correct for machines also makes it correct for people.
0.2%
of sessions
came from agents on enterprise sites, in the figures we could verify.
11%
of consumers
say they would let an AI complete a purchase on their behalf today.
2027
Gartner expects
more than 40% of agentic projects to be cancelled before the end of it. We do not sell agent traffic.
$ connect.arliwork.com --diagnose
Start with one domain
Send a domain and a product line. We run the diagnostic and send the transcript before any invoice.
hq@arliwork.com · Shenzhen Capernaum Technology Co., Ltd · PIAKHOUSKI DZMITRY