> ## Documentation Index
> Fetch the complete documentation index at: https://enrichment-docs.verzla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enrichment API

> Enrich the Verzla catalog with AI-generated attributes, descriptions, and metadata — at scale, with confidence.

The **Verzla Enrichment API** is a REST surface for trusted third-party providers that enrich a
merchant's product catalog. You read products and the merchant's attribute templates, generate
proposals with your models, and submit them back as **pending revisions** for a human reviewer to
accept or reject.

Nothing you submit goes live automatically. Every proposal lands as a revision in the merchant's
review queue, so your integration can be bold while the merchant stays in control.

<CardGroup cols={2}>
  <Card title="The Pipeline" icon="diagram-project" href="/enrichment/pipeline">
    Understand the read → enrich → submit → review loop before you write any code.
  </Card>

  <Card title="Quickstart" icon="bolt" href="/enrichment/quickstart">
    From API key to your first accepted proposal in a handful of requests.
  </Card>

  <Card title="Request an API Key" icon="key" href="/authentication/request-api-key">
    Every call is authenticated. Start here — you cannot read or submit without a key.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Every endpoint, with request and response shapes and copy-paste examples.
  </Card>
</CardGroup>

## What you can do

<Steps>
  <Step title="Fetch attribute templates">
    Read the merchant's [attribute templates](/enrichment/attribute-templates) first. They define
    the schema — which attributes matter, their units, data types, and priority — so your model
    enriches against the right shape instead of guessing.
  </Step>

  <Step title="Fetch products">
    Pull the catalog as a [paginated list](/enrichment/fetching-products#paginated-export) (with an
    optional `modifiedSince` filter for incremental syncs) or [look up specific SKUs](/enrichment/fetching-products#fetch-by-sku).
  </Step>

  <Step title="Submit proposals with confidence">
    Send enriched fields back as a [submission](/enrichment/submitting-proposals). Attach a
    `confidence` score (0–100) to each item so reviewers can triage high-confidence work first.
  </Step>

  <Step title="Track your acceptance rate">
    Check [how your proposals are performing](/enrichment/acceptance-rate) over time and tune your
    models against real reviewer feedback.
  </Step>
</Steps>

## Base URL

All endpoints are served under a single base URL and the `/api/enrichment` prefix.

```
https://api.verzla.com/api/enrichment
```

<Info>
  Ask your Verzla contact for the exact base URL for your environment — staging and production
  differ. Every example in these docs uses the placeholder above.
</Info>