Prove the problem, serve the catalogue, sign the claims
The gateway is the core of what we build. The diagnostic exists so you never buy it on faith, and the records exist so what an agent relays about you can be checked by someone who trusts neither of us.
Three ways a catalogue fails an agent
187 of the 189 we measured fail on all three counts at once. Any one of them is enough to lose the quote.
| Failure | What it looks like | Measured |
|---|---|---|
| Closed to machines | A script gets 403 while a browser gets 200. Every agent is lost at the door, and you cannot tell which of them was a buyer. | 94 of 189 |
| Readable, not machine-readable | The page renders and a price exists, but nothing states it in machine terms, so the agent sees a range or gives up. | 94 of 189 readable 0 with a price |
| Nothing to ask | An agent can fetch a page. It cannot ask what you have in a part number, in stock, for this account. No endpoint, so no answer. | 189 of 189 |
Three products, and what each one costs
Agent-readiness diagnostic
A live agent run against your public surface and, under NDA, against your catalogue. You receive the raw transcript rather than a score: every request, every response code, every field, and the searches that returned nothing.
- Which of your product lines an agent can quote, and which it cannot
- What a competitor does differently on the same query
- One domain, five working days
Catalogue gateway for agents
A managed MCP and REST layer over the catalogue you already run, reading it where it lives instead of copying it to us. An agent gets answers, you keep the source of truth.
- Read-only for the first month
- Your VPC or ours, SSO on the control plane
- Access rules and per-buyer pricing stay yours
Verifiable claims
The facts an agent relays, signed, with the basis of each claim stated separately: measured, self-declared, or asserted by a named third party. A checker sees who asserted what, and whether anything changed since.
- Keys published for offline verification
- Revocation list for withdrawn records
- No account needed to verify
Four steps, and your data never leaves
The gateway is a reader, not a warehouse. It sits in front of the systems you already run and answers questions on their behalf, under rules you set.
The same question, before and after
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.
Six tools, and nothing else in the first version
Small surface on purpose. Everything around these six calls is access control, metering and the log. Fourteen more tools would triple the integration and change nothing about whether an agent gets a correct answer.
The same tool called anonymously returns the list price or a refusal, depending on the rule you set. The gateway never decides who deserves which price, it enforces the rule you already have.
Who sees what, and how month one runs
| Caller | What it can see |
|---|---|
| An anonymous agent | Public availability, and list price only if you publish one |
| A registered buyer's agent | That buyer's negotiated price, contracted stock, their own documents |
| An internal agent | The full catalogue, including lines you never publish |
| Our operators | Metadata and logs. Never your prices, and never the contents of a buyer's agreement |
Diagnose
We run the scan, then the deeper agent pass under NDA, and deliver the transcript with the gaps listed by product line.
Scope
You pick one product line, the endpoints the gateway may read, and the response rules for each class of caller.
Connect
The gateway goes live behind your identity provider, in read-only mode, with the log switched on from the first call.
Review
We read the query log together: what was asked, what was refused, what an agent misunderstood. Permissions move only after that meeting.
What we deliberately do not do
No writes to your systems
No order, no price change and no stock adjustment reaches you from us, ever.
No copy of your catalogue
Your product data stays where it lives. We hold no shadow database that drifts from your source of truth.
No promises about traffic
We cannot make agents arrive. We can make sure that when they do, they get a correct answer.
Put one catalogue in front of agents
One product line first. We quote the integration after the diagnostic, not before, because what it costs depends on what the diagnostic finds.
hq@arliwork.com · Shenzhen Capernaum Technology Co., Ltd · PIAKHOUSKI DZMITRY