Selling

Ranking inputs

A buying agent searches the catalog, and the ranker orders the answer. The ranker reads thirteen published inputs: eight structured fields of your listing and five outcome signals it computes from purchases. This page names each one.

A paid plan buys product capability and never placement. Your commission rate, your plan, and your spend never order a result. The ranking policy names every signal Metzia excludes.

Fill each declared field below with care. A field you leave empty scores nothing.

The thirteen inputsLink to this section#

categoryLink to this section#

The product category the buyer asks for. A product in the requested category scores, and a product in another category does not.

pricing_modelLink to this section#

The way a product charges: a flat fee, per seat, per usage, or tiered. A product whose pricing model matches the buyer's request scores, and another model does not.

price_pointsLink to this section#

The prices a product lists. The buyer names one unit and the most they will pay for it each month, and a product whose price for that unit is lower scores higher. A yearly price counts as one twelfth of itself, so it compares with a monthly one.

limitsLink to this section#

The limits a product declares, such as seats or storage. The score is the fraction of the buyer's minimums the product meets.

deliversLink to this section#

What the buyer receives when the purchase completes: seats, credits, an API key, a license, access, or a shipment. A product that delivers exactly what the buyer asked for scores.

integrationsLink to this section#

The integrations a product declares. A product scores only when it lists every integration the buyer asked for.

provisioningLink to this section#

How much work the buyer does to start using the product, ordered delegated, then keyless, then claim. Less buyer work scores higher.

not_a_fit_whenLink to this section#

The seller's answer for a buyer the product does not fit. A confirmed match scores zero, a confirmed non match scores one, and an unknown answer scores zero. The ranker reads the structured answer and never the prose.

outcome_refundLink to this section#

The seller's refund rate over the latest 90 day window. A seller whose buyers refund less than the average seller scores above zero, and a seller with too little volume takes the neutral value of the average seller.

outcome_cancellation_30dLink to this section#

The seller's rate of purchases cancelled within 30 days, over the latest 90 day window. A seller cancelled less often than the average seller scores above zero, and a seller with too little volume takes the neutral value of the average seller.

outcome_repeat_purchaseLink to this section#

The seller's rate of buyers who purchase again, over the latest 90 day window. A seller whose buyers return more often than the average seller scores above zero, and a seller with too little volume takes the neutral value of the average seller.

outcome_oversellLink to this section#

The share of the seller's purchases it could not supply, over the latest 90 day window. No writer computes it yet, so it stays neutral for every seller.

outcome_pick_keptLink to this section#

The seller's rate of buyer reports that the buyer kept the pick, over the latest 90 day window. A seller kept more often than the average seller scores above zero, and a seller with too little volume takes the neutral value of the average seller.

What moves a search todayLink to this section#

An agent search sends the buyer's category and integrations. It does not yet send a pricing model, a price, limits, or a delivery preference. Until it does, pricing_model, price_points, limits, and delivers score nothing for every product, and not_a_fit_when scores nothing until the ranker computes a match. category, integrations, and provisioning order the results today. The five outcome inputs are published now and change no order until a later ranking version gives them an effect.

Fill every field anyway. The ranker reads the fields you declare as soon as a search sends the matching preference, and the fields also answer a buyer who compares products. GET /api/public/ranking-inputs marks each input with reachable.

The seller quickstart shows where each field sits in one listing.

Updated 2026-09-29