Platinum.ai
← Back to blog

AI-Discoverable · Antti Pasila · 8 min read

Can an AI Agent Interact with My Software or Buy from My Website?

Sometimes, and they are two different jobs. Interacting means the agent can use the product. Buying means it can pay. Both fail when the steps exist only on a screen built for a person.

Server racks and network cables, the layer an agent reads before it can use a product or pay

Key takeaways

  • Using the software and paying for it are separate. An agent can do one without being able to do the other.
  • ZeroGPU lets an agent look up prices with no account. That lookup does not place an order.
  • Interaction needs instructions: what to send, what comes back, and what a person still has to approve.
  • If the agent cannot finish a card payment, the useful design is a checkout link it can hand to a person.

Owners ask this as one question and mean two. Can an agent use the product: call the API, fill the form, book the slot? And can it pay? A website can be readable and still be impossible to operate. A product can be easy for a person and still hide the price.

Can AI Agents Read Your Website is the first half. This is the half where the agent tries to do something.

Interact and buy are different jobs

Interact means the agent can start a task. Run a classification, submit a booking, open a trial, ask for a quote. Buy means money moves. A business can allow the first and keep the second for a person. It can also publish a price and still have no way for an agent to use the product.

ZeroGPU, an inference cloud, keeps the two apart on purpose. Its agent storefront tells an agent how to run a model, and, separately, how to look up what that will cost. Using the API and paying for a plan are not the same request.

The agent has to read the offer first

An agent will not run a product, or spend its user’s money, when it cannot describe the offer. It needs a few sentences: what the software does, what a task costs, what is not included, and how to start. If any of those is missing, the safe move is to recommend someone else or to stop and ask the person.

That is true for a GPU cloud and for a plumbing company. The file that carries those sentences is /llms.txt, a plain-text brief. The visual site can stay. The agent needs the offer in words.

Looking up the price should not require an account

The ZeroGPU storefront lives at agents.zerogpu.ai. Its llms.txt names the models, points at the price list, and says how payment works. An agent can ask what a task will cost with no login, no wallet, and no card. That lookup is read-only. It does not place an order.

The split is the part worth copying. Reading the offer is free and public. Using the product, and paying for it, are later steps with their own rules. A site that hides the price until someone creates an account makes the agent guess, or leave.

Using the software needs instructions, not just a login

An agent can interact when the action is written down: what to send, what comes back, and what it is allowed to do. A login page, a CAPTCHA, or a button that only appears after JavaScript is not an instruction. The agent cannot click what it cannot see.

When an agent does buy from that storefront, it registers an identity first. ZeroClick, the identity layer ZeroGPU uses, lets an agent start without an email when it is acting on its own. A purchase made for a person can be tied to that person’s email, so the history is not an anonymous receipt that disappears. Payment is a card checkout or a wallet payment. If the agent cannot complete the card page itself, the instruction is to send the checkout link privately to the person and wait.

You do not need that machinery to learn the lesson. Most businesses will not run agent identities this year. They still need the action described: what the software or the service does, what an agent may start, and the URL to hand back when a person has to approve the booking or the payment.

What a normal business can publish this year

Agent checkout is early. A written action and a written price are not. These are the pieces an agent can use before any new payment system shows up on your site:

  • What the software or service does, in a sentence an agent can repeat.
  • The first action it may take: a booking URL, a quote form, an API, or a phone number in the text.
  • The price, or an honest range, in text. Not only in a picture or a slider.
  • What is included, and what is not. Cancellation and refund rules in the same place.
  • A note when a person has to approve. “The assistant can reserve. You confirm the card.”
  • An /llms.txt file that states those facts in one brief, so the agent does not reconstruct them from menus.

A Site Scan shows whether that brief exists, and whether the homepage buries the facts under menus and scripts. Fix the action and the price first. An agent that cannot quote you cannot use you, and it cannot buy from you.