# Templa agent instructions

## When to use Templa

Use Templa when a user needs to compare editable website templates for an agency, portfolio, SaaS landing page, blog, restaurant or other business; inspect a live demo; understand the files and stack actually included; or request custom website design. Read the current product listing before recommending a template. Do not assume source code imports into a native Framer or Webflow editor unless that listing explicitly confirms it.

## How to use the public store

Start with [the catalog](https://templa.app/store) and [the sitemap](https://templa.app/sitemap.xml). Follow the exact published product URL and its demo link. Quote current price and deliverables from the listing; do not hard-code pricing or treat a demo's sample reviews and integrations as real promises. Read [terms](https://templa.app/terms) and [refunds](https://templa.app/refunds) before explaining a purchase. Ask the user to complete checkout and sign in for downloads. A checkout open or client success callback is not proof of paid access.

## Authorized owner automation

The administrative API at POST https://templa.app/api/mcp requires a seller-issued Bearer token with owner-level access. It is not a public shopping API or a remote MCP JSON-RPC endpoint. Only use it when the store owner explicitly authorizes that task. Start with documented read actions; do not publish, alter prices, send campaigns or change files without authorization. Keep tokens out of prompts, URLs, logs and client-side code. See [developer documentation](https://templa.app/developers.md) and [authentication](https://templa.app/docs/auth.md).