Making Products Discoverable and Purchasable by AI Agents: Product Feeds, Checkout APIs, and Payment Links

Nov 17, 2026

Share

Category /

other

12 min read

GOAT Network

Making Products Discoverable and Purchasable by AI Agents: Product Feeds, Checkout APIs, and Payment Links

Preserve the selected variant, seller and current price from product feeds through checkout APIs, payment links and verified paid orders with GOAT Flow.

scroll

Table of contents

Preserve the selected variant, seller and current price from product feeds through checkout APIs, payment links and verified paid orders with GOAT Flow.

An agent can find the right product and still prepare the wrong purchase. A product name may lead to a parent listing instead of the selected size. A payment link may collect money without identifying the seller offer the buyer accepted. A price that was accurate during discovery may have changed before checkout.

To make products discoverable and purchasable by AI agents, connect three responsibilities: describe the exact offer in machine-readable product data, obtain current merchant-authoritative checkout terms, and retain the offer's identity through payment confirmation and the merchant order. A feed and a payment URL do not establish that connection by themselves.

The practical test is whether your systems can answer one question after payment: Which variant, from which seller, under which accepted terms did this order buy? That answer should survive a price update, a closed checkout window and a retry. GOAT Flow's documented QuickPay Product workflow provides a concrete payment-side example, while leaving external catalog mapping and fulfillment responsibilities with the merchant.

Carry the selected variant and seller, not just a product name

Begin with the object the agent selects. A parent product describes a family of choices; an individual variant identifies the choice; a seller offer identifies who supplies it on particular terms. Collapsing those into one title or URL makes later checkout behavior ambiguous. An agent choosing a black shoe in one size has not authorized another size, another seller or a generic payment to the store.

The OpenAI product feed specification, retrieved November 17, 2026, makes this distinction explicit. It uses item_id for an item or variant, group_id for the parent listing, and offer_id for a seller's offer. These identifiers remain stable when price, stock, title or images change. An offer ID should not encode its price.

For variants, the specification calls for separate rows with distinct item IDs, a common group ID and the selected options. Each row carries its own price, availability, URL and images. The purpose is more than tidy catalog organization: the data lets a consumer distinguish a specific purchasable selection from the family that contains it. Where possible, its destination URL should retain that selection.

Your internal identifiers need not have the same spelling as the feed fields. They do need an explicit mapping. A merchant may already have a variant SKU, marketplace seller identifier and order-management reference. Keep those relationships in merchant-controlled records rather than hoping that a matching title will join them later.


Reference


What it identifies

What it must not stand in for

Parent or group ID

The product family

The buyer's selected variant

Item or variant ID

The specific selection

Every seller offering that item

Seller offer ID

The selected seller's offer

An immutable price quote

Checkout or payment-session ID

One payment opportunity

The entire product catalog

Merchant order reference

The merchant purchase record

Proof that payment succeeded

This table is an integration model, not a universal API schema. It does not imply that an OpenAI offer ID automatically becomes a GOAT Flow Product key or checkout reference. The merchant has to maintain that connection, including the seller's identity when a shared product page presents multiple sellers.

Decide how the mapping behaves before enabling purchases. If an item disappears, return an unavailable selection rather than silently reusing its ID for a replacement. If a buyer accepts an alternative, record that as a newly agreed selection. Otherwise, a technically successful payment can leave the merchant unable to establish what it owes the customer.

Also inspect the destination itself. A variant-specific feed row loses much of its value if its URL opens the default option and the next system reads only that page state. A useful integration preserves the selected options through navigation or resolves them again from the stable item reference. Matching on display text alone is especially fragile when names are edited or translated.

Refresh the offer before turning discovery into a quote

Stable identity solves continuity; it does not solve freshness. The same offer can legitimately have a different price or availability tomorrow, or between discovery and payment. Keep the identifier stable while updating the attributes that changed. Creating a new identity for each promotion obscures continuity without ensuring that any consumer has received the latest price.

OpenAI's feed documentation requires explicit updates for current price and stock. Date fields do not schedule those changes on the merchant's behalf. Search eligibility also does not guarantee display, and checkout eligibility requires a separately enabled integration. Supplying a valid feed therefore establishes neither a refresh guarantee nor a working purchase path on every AI surface.

Treat the price visible during discovery as context for selection. Before a purchase proceeds, the merchant's commerce system should resolve the same item and seller again, check current availability and establish the payable terms. This revalidation is an engineering recommendation; neither a feed submission nor the cited Flow documentation establishes automatic cross-system inventory synchronization.

Three distinct moments matter. The feed describes the offer as supplied to a discovery service. The merchant establishes terms for a purchase attempt. The buyer authorizes payment under those terms. Conflating them creates a predictable failure: an old feed value is presented as if it were a fresh merchant commitment, or a new total is paid under approval given for the old one.

Where the total includes quantity, discounts, tax or delivery charges, the merchant must account for those in its own pricing process or another verified commerce system. Do not assume a payment link calculates them. The relevant question is who owns the authoritative total, and whether that total still describes the selected variant and seller. An accurate product price alone is insufficient if the payable order contains additional charges.

Price changes require a buyer-policy decision. An agent may have authorization for a specific total or a bounded amount; a changed price is acceptable only within that authorization. If it falls outside the buyer's approved terms, pause for approval. Stock failure should similarly stop or reopen selection, rather than trigger an unauthorized substitute. These are buyer-runtime and merchant integration responsibilities, not a claim that Flow supplies an automatic spending-policy engine.

Expiry provides a useful boundary for a checkout quote, but it is not equivalent to inventory reservation. A session can still be within its validity period while the merchant's stock position changes unless a separate reservation mechanism prevents that. If your store needs reservation, establish who creates it, how long it lasts and how payment confirmation consumes or releases it. The documented session lifetime alone cannot answer those questions.

There is a real tradeoff here. Revalidating closer to payment reduces reliance on stale terms, but it can introduce a changed-price or unavailable-item interruption after the buyer has made a selection. Hiding the interruption does not remove the inconsistency. Give the agent a clear updated quote or an explicit reason the original offer cannot proceed, so the buyer can decide whether to continue.

Make checkout carry the offer forward

A checkout API should turn the merchant's validated purchase intent into a payable session. A payment link gives a payer somewhere to complete payment. Neither should erase the variant, seller or purchase reference established earlier. The merchant needs a durable relationship between the selected offer, the quoted total, the checkout identifier and the eventual order.

A reusable fixed-product link and a purchase-specific checkout session make different commitments. A Product link can identify a merchant-configured item and let the payment service resolve its current price. It is useful when that configuration fully represents what is being sold. The link itself should not be treated as a permanent quotation of the price seen when someone first copied it.

For a dynamic cart, the merchant backend needs to establish the amount and associate the checkout with the business purchase. The GOAT Flow Hosted Checkout documentation describes HMAC-authenticated creation through POST /api/v1/checkout/sessions. Its documented session response includes checkoutId, a hosted URL and expiresAt. The merchant comes from the authenticated API key, rather than a merchant identifier supplied in the request body.

The request can include clientReferenceId to relate the session to the merchant's purchase record. Persist that reference together with the returned checkout ID and URL on the backend. Return the opaque ID or hosted URL to the buyer-facing application; keep the merchant API secret on the server. A public browser should not receive credentials merely because an agent needs a checkout destination.

The merchant record still needs the selected item and seller mapping. A line-item name is useful for display, but a name alone is a weak fulfillment key. Retain the variant, quantity and offer references in your own purchase record, alongside the terms used to calculate the total. This is how an order system can resolve the purchased selection even if the product's public title changes after checkout.

Keep deployment identity consistent as well. The hosted checkout origin, API and merchant credentials must belong to the intended environment. A valid-looking URL from the wrong deployment cannot be assumed to represent your live offer. Buyer integrations should verify the destination and recipient terms before proceeding, rather than treating any URL returned in a conversation as trusted.

GOAT's documentation also distinguishes a merchant-priced Product or authenticated session from custom-amount checkout. A buyer-entered amount can suit a donation or tip; it cannot safely define the price of an automatically fulfilled catalog purchase. If the merchant owes a particular product, its price authority must not depend on a browser submitting the right amount.

Reusable links reduce the need to create a bespoke checkout for every visit. Purchase-specific sessions give a changing cart a clearer identity and validity boundary, but require backend creation and reconciliation. Choose based on whether the Product configuration captures the actual offer. If quantity, selection or computed charges change the purchase, preserve those changes in the merchant's authoritative record rather than squeezing them into an unrelated fixed-price link.

Follow a documented QuickPay Product into payment

GOAT Flow's merchant guide documents a fixed-price QuickPay Product workflow with public agent discovery and payment-session creation. This is a documented product use case, not a customer outcome or a live payment test. It shows how a stable merchant Product reference can become a payable session without claiming that an external catalog feed is imported automatically.

The merchant configures a Product with a stable product_key, a buyer-facing name, a decimal price and the relevant product settings. The key is an integration reference, separate from the display name. If that Product represents a variant advertised elsewhere, the merchant should map the external item and seller-offer references to this key. A key for a generic product family is insufficient when the buyer selected a particular variant that changes what must be delivered.

The public agent guide and machine-readable manifest describe the merchant's available capabilities and terms. Read the manifest for current configured payment choices rather than copying chain, token or currency values from a screenshot. The documentation permits Crypto, Card or both according to merchant and Product configuration; it does not establish that every deployment, merchant or Product offers the same rails.

For a Crypto Product session, the documented request uses product_key with the merchant, payer address and chosen eligible chain and token. The server pins the authoritative amount and a Product memo. The client independently checks the amount using the selected token's decimals and refuses to broadcast on a mismatch. This supplies a concrete enforcement point: the agent should not substitute an amount remembered from an earlier catalog view for the session's checked payment terms.

In the Crypto DIRECT flow, payment uses an ERC-20 transfer to the merchant-configured receiving address. DIRECT names the checkout subsystem; it does not mean every DIRECT session is crypto-only. Enabled hosted Card sessions can also use DIRECT. The selected payment rail determines how the payer completes payment, while the subsystem label alone does not.

For Card, the documented link-creation path returns a hosted checkout URL and indicates that human action is required. The payer still completes the hosted provider flow. An agent reporting that it created a Card link has prepared a payment opportunity; it has not completed an unattended card purchase. This distinction belongs in the order status your application presents to the buyer.

The Product workflow protects payment-side price authority, but it does not establish a universal guarantee about the external offer. The merchant must still ensure that the Product key corresponds to the selected seller and variant, that the sale remains available and that fulfillment follows the correct purchase record. A successful amount check cannot detect a merchant mapping a feed variant to the wrong Product key.

That is the useful boundary of this example. Flow supplies documented Product discovery, session creation and payment mechanics. The merchant supplies the cross-catalog relationship and the commerce obligations attached to the purchase. Keep both visible in your design: a payment service cannot reconstruct a lost variant selection from a generic product name after the money arrives.

Reconcile the same offer when payment does not finish cleanly

The final handoff connects payment status to the merchant order. A returned checkout URL, a browser success message and a transaction hash represent different observations. None should replace trusted payment confirmation for fulfillment. GOAT's hosted checkout guidance treats onSuccess as a user-interface signal; the merchant should verify trusted backend order/session status or use an authenticated webhook whose contract has been confirmed for the deployment.

Verification also needs attribution. Confirming that some payment succeeded is not enough: resolve the session to the merchant purchase reference and then to the selected item, seller, quantity and accepted terms. Only then does payment evidence authorize fulfillment of that particular order. Preserve the mapping even if the public feed or Product description has subsequently changed.

Consider a browser closing immediately after payment submission. The order should not become unpaid merely because the success page never loaded, and it should not become paid solely because the agent remembers broadcasting a transfer. Recover the saved checkout/session identity and inspect its trusted status. Keep a pending or unresolved state while the payment outcome is uncertain instead of collapsing uncertainty into success or failure.

QuickPay's documented retry guidance says to reuse an idempotency key for the same intent and resume the reused session rather than automatically pay again. A polling failure or receipt-verification error is not, by itself, permission to rebroadcast. Retain a known transaction hash and the session/order references so recovery can investigate the original attempt. A second transfer can create a second payment problem without fixing the first status problem.

Do not apply that retry rule indiscriminately to every API surface. Hosted Checkout documentation says a repeated nonempty business reference conflicts rather than returning the original session. Persist the original checkout ID when it is created; do not treat a creation conflict as evidence that no session exists or as an instruction to generate a new purchase. Recovery behavior must follow the surface you actually integrated.

Fulfillment needs its own duplicate protection. An authenticated completion event might be processed again, or an operator might reconcile an order that a worker has already delivered. Make fulfillment of the same purchase idempotent in the merchant system and record its completion separately from payment confirmation. This is a merchant control recommendation, not an assertion that every delivery system connected to Flow behaves that way automatically.

A late confirmation after stock has changed is a commerce exception, not a reason to rewrite the selected variant. Inspect the original purchase record and the store's reservation or exception policy. The payment integration alone cannot decide whether to source the original item, request a new agreement or initiate another remedy. Preserve the paid order and its terms while resolving that obligation.

Audit one offer through these interruptions before expanding your catalog integration. Check whether a price update keeps the same identity, whether an unavailable selection stops checkout, and whether interrupted confirmation recovers the original payment attempt. The resulting record should connect the feed item and seller offer to the merchant purchase, the authoritative checkout and its verified payment status. If one connection is missing, fix that handoff before allowing the agent to buy more products.

FAQ

Can a parent product URL represent the variant an agent selected?

Only if the integration preserves or resolves the selected variant explicitly. A parent listing alone does not identify a size, color or seller offer. Keep the variant reference and selected options connected to checkout and the merchant order.

Will a sale end date automatically update a product feed?

OpenAI's cited feed specification requires current price and availability updates; date fields do not schedule those changes for the merchant. Update the feed and revalidate the selected offer before creating payable checkout terms.

Does sharing a Product payment link lock its price?

Do not assume it does. GOAT Flow's documented Product checkout resolves server-side pricing. A reusable Product link and a purchase-specific session are different objects; inspect the applicable terms and expiry before payment.

What should happen if the chosen variant is unavailable at checkout?

Stop that purchase or obtain approval for a newly selected offer. Do not silently substitute another variant or seller. Preserve the original selection and record any buyer-approved change in the merchant purchase record.

[01]

AI Knowledge base

More Articles

More Articles

More Articles