---
name: paz-api
description: Use the Paz.ai Public API and MCP server for authenticated catalog, AI shopping visibility, organization, and optimization workflows.
metadata:
  author: Paz.ai
  version: "1.0.0"
---

# Paz.ai API skill

Use this skill when an authorized commerce team asks an agent to inspect Paz.ai monitoring data, catalog data, readiness scores, organization configuration, or supported optimization workflows.

## Discovery

1. Read https://www.paz.ai/openapi.json for REST operations and typed schemas.
2. Read https://www.paz.ai/.well-known/mcp.json for the MCP endpoint and protocol metadata.
3. Read https://www.paz.ai/auth.md before requesting credentials.

## Authentication

Use a scoped Paz.ai API key in the X-API-Key header. Send credentials only to api.paz.ai. Never print, log, or store the key in generated artifacts.

## Safe operation

- Prefer read operations unless the user explicitly asks for a write.
- Before a write, state the organization, resource, fields, and intended change.
- Do not broaden scopes, enumerate foreign identifiers, or infer access from error differences.
- Treat visibility results as observations, not causal proof that a catalog change produced an outcome.
- Preserve merchant review and approval boundaries for catalog changes.

## Common workflows

- List monitored queries and ranking-check results.
- Read visibility and competitive score time series.
- Inspect catalogs, products, transformations, and AI-readiness scores.
- Read organization profile, voice, theme, competitors, aliases, merchant information, and feature settings.
- Use MCP tools when the client supports Streamable HTTP; otherwise use the equivalent OpenAPI operation.