Quick start
Get productive in CataZenta in one session. Choose how you work — the platform is the same underneath.
| Path | Best for | Time |
|---|---|---|
| UI-first | Merchandisers, catalog managers | ~30 min |
| API-first | Developers, integrators | ~15 min |
| AI-first | Teams using Claude, ChatGPT, Cursor | ~20 min |
Not sure? Use Choose your path.
UI-first (merchandisers)
Goal: Create a governed product and see completeness before export.
- Sign in to your tenant’s PIM URL (from onboarding).
- Read Catalog fundamentals — setup order matters.
- Confirm product family and channel exist (ask admin if not).
- Create a product in the UI.
- Fill attributes for at least one locale on your target channel.
- Open completeness — guide.
- Optional: Export to channel when score is green.
Next: Using the PIM UI · Workflows
API-first (developers)
Goal: Prove API access and list catalog data.
- Obtain credentials from your admin (email + tenant UUID).
- Authenticate — save
access_token. - First API call — list products and verify
/auth/me. - Create a product in a family.
- Browse OpenAPI reference or download specs from API tools.
Headers on every call:
Authorization: Bearer <access_token>
X-Tenant-Id: <tenant-uuid>
Full detail: API authentication.
Next: Recipes · Service account
AI-first (agents)
Goal: Connect an AI assistant to live, permissioned catalog operations.
- Skim AI Product Intelligence.
- MCP quickstart — endpoint, OAuth, tenant.
- MCP tools — what agents can read and write.
- Try a workflow: Amazon-ready content.
Agents use the same permissions as the user who connected MCP — not a shadow database.
Next: Agent workflows · Zen AI
Everyone — catalog foundation
Whether you use UI, API, or AI, these concepts are shared:
| Topic | Doc |
|---|---|
| Families, attributes, channels | Catalog fundamentals |
| Security & trust | Security |
| Why teams switch to CataZenta | Why CataZenta |
Production access
- Trial / demo tenant: Book a demo
- API credentials: Your CataZenta admin or account team
- Support: Contact link from your onboarding email