Skip to the content

DocsBuild an agent

Infrastructure and prices

What an agent runs on: how each vendor's prices are read and checked, the reference jobs, and why no vendor is chosen for you.

An agent that runs code, searches the web or drives a browser runs on someone's product. The infrastructure directory lists those products with each vendor's own prices, and a stack answer prices them for the agent you describe. Nothing here says which is better.

Where the prices come from

Infrastructure lists what an agent runs on: sandboxes, browsers, search, runtimes and brokers. It is a short list kept by hand, not a crawl. A product is here because someone added it to a file in this site's repository, and being here says nothing about whether it is good.

Every price was read by a person from the vendor's own pricing page and written down twice: the number, and the amount exactly as the page prints it. Prices are in the vendor's own units (a vCPU-second, a browser hour, a thousand requests, a credit) and are not converted. The cheapest region a page lists is the one taken; an enterprise or committed-use price, and a GPU, are left out.

Each night the catalog job fetches each of those pages, with no credential, and looks for every amount on it. When all are there the product's page says the day. When one is missing, the page says "not confirmed since" that day, and after a week of it the product's prices are set aside: shown, marked, and left out of any comparison until a person has read the page again. A page that could not be fetched is not a missing price, and starts no count.

What that check proves is narrow. It proves an amount is still printed. It does not prove the amount still means what it did: a vendor can keep a price and change what an hour is, or what a plan includes. The vendor's page is the last word, and every product's page links it.

Some products have no price here. "Prices not read yet" means nobody has read the page into the file. "Not comparable" means the vendor sells plans whose terms differ in kind, with no rate for a unit.

One job, priced on each

The vendors' units do not line up, so a category's page prices one stated job on every product that sells it: an hour of a sandbox with 2 vCPU and 4 GiB of memory, an hour of a browser, a thousand searches. The job's sentence is on the page, and every figure has its sum, so it can be checked by hand. A figure is at listed rates: no plan fee, no free allowance, no storage or transfer, and a vendor's GB counted as a GiB. It is what that job comes to there, not what your agent will cost, and how busy a sandbox is can change which product comes to least. A second table says which plan comes to least at a few monthly volumes, fees and allowances included.

Nothing is ranked. A job's table is in the order of what the job comes to, least first, with the figure in the row, and a product with no figure for it after those, by name. That is an order by one number for one stated job, not a view of which product is better. Every other list is products with prices first, then by name.

In a stack answer

When the request implies infrastructure, the answer has an infrastructure part for each kind: a sandbox when the agent runs code, and search, reading or a browser when needs asks for them. A request that implies none has no such field. Each part says why it is there (because), what was priced (basis), and lists the products priced for it in options, least first, each with usd, the sum behind it and the day its vendor's pricing page last printed the prices used. The products and their prices are the infrastructure directory's, described above.

The basis is your usage only if you state it. With infra.usage, a figure is a month's bill on the product's cheapest plan for that usage: the plan's fee, each price after what the plan includes that month. Without it, a figure is a stated reference job (an hour of a 2 vCPU sandbox, a thousand searches) at listed rates, the part names the job, and assumptions says so. Nothing is guessed about what your agent will use. Always show the sum with a figure; it is one string so that it can be.

A model's cost is never added to these. One is a price for a call, the other for a month or a job, and a total of the two would be a number with no receipt.

Why it does not choose a vendor for you

For a system, the choice is its owner's own server: there is a fact to choose by. For infrastructure there is none. No product is "the owner's own", and nothing here measures which sandbox or which search is better. Price is the only thing the catalog knows, and choosing by price alone among every vendor would be an endorsement by price.

So with no vendor named, a part has options and no choice. Name the vendors you already have accounts with in infra.vendors and the part's choice is the one of those that comes to least for the basis, with rule saying so: cheapest_of_named, or only_named when one was. That is the same sentence the model answer starts from: on what you already use. An order by price is not a ranking, and a listing is not an endorsement.