# Payments and marketplace

> Field reference for the model marketplace, covering the catalog card, purchasing a model, and the resulting API key.

The model marketplace lets you purchase model access from connected gateways, paid for on-chain via x402 and provisioned automatically as a usable API key. For the conceptual model, see [Trust-fabric integration](/products/affinidi-trust-fabric/agent-stream/concepts/trust-fabric-integration.md).

## Catalog entry

The dashboard has two places to browse the marketplace: a top-level Marketplace page, and a per-gateway Marketplace tab on a remote gateway’s edit page (shown only when that gateway is a remote gateway exposing a marketplace channel). Both render the same catalog card (image, heading, badges, body text), not a labeled settings form.

| Field | Description |
| Name | Card heading. |
| Provider | Shown as small text under the name, and as the card image’s alt text. |
| Logo | Card image. |
| Rating | A star icon, the numeric rating, and the review count in parentheses, e.g. ★ 4.8 (312). |
| Context Window | Shown as text, e.g. “Context: 128K”. |
| Category | Shown as a badge on the card, and used for the browser’s filter buttons (a plain button per category, plus two synthetic buttons, All and Purchased, alongside the real category names). |
| Description | Shown as body text on the card. |
| Pricing | Shown as text on the card. Distinct from the on-chain purchase price shown next to the purchase button (see below). |
| Capabilities | Shown as a row of badges on the card (square-cornered, not rounded pills). |
| Gateway Name | Shown as a badge on the card, only when browsing an aggregated, multi-gateway catalog. |

## Purchasing a model

Selecting Purchase Key on a catalog card (its price shown alongside in USDC) starts an on-chain payment. Once it settles, click Save API Key to Gateway in the confirmation dialog to provision the API key and save it to your [Secrets](/products/affinidi-trust-fabric/agent-stream/reference/security/secrets.md) store; Skip for now closes the dialog without creating a secret, even though the payment already went through. That turns a model listed by a connected gateway into something a surface on your own appliance can actually call, with no separate provider account to create and no key to copy in by hand.

- Purchase when a surface needs a model that isn’t already covered by an existing provider key. Check your [Secrets](/products/affinidi-trust-fabric/agent-stream/reference/security/secrets.md) store first so you don’t pay for access you already have.

- If you skip saving the key right after payment, you’ll need to purchase again to get another chance to save it — the payment itself isn’t refunded or reused.

- Renew ahead of expiry for any model backing a production surface, since an expired key stops working until renewed; don’t let it lapse on something in active use.

| Status | Meaning |
| Purchase Key | Not yet purchased. |
| Purchased, with “Expires {date}” shown alongside | Purchased and currently valid. |
| Renew Key (Expired) | A previous key has expired; purchasing again provisions a new one. |

## Related

- [Secrets](/products/affinidi-trust-fabric/agent-stream/reference/security/secrets.md): Where a purchased model’s provisioned API key is stored.

- [Trust-fabric integration](/products/affinidi-trust-fabric/agent-stream/concepts/trust-fabric-integration.md): The conceptual overview of x402 payments and the model marketplace.

- [Gateways and connection points](/products/affinidi-trust-fabric/agent-stream/reference/trust-fabric/gateways.md): Connected gateways whose models appear in an aggregated marketplace catalog.

- [Cost and usage limits](/products/affinidi-trust-fabric/agent-stream/reference/surfaces/cost-and-usage-limits.md): Budget controls for using a purchased model once wired into a surface.