Getting Started

ACE (Agentic Commerce Engine) enriches product feeds and generates PDP content (descriptions, meta tags, JSON-LD, feed formats) from your catalog data.

Use ACE at https://ace.authoritas.com. Sign in, manage API keys under Settings, Developer console, and call the API from that base URL.

What is ACE?

You send product data (titles, descriptions, images, categories) and ACE helps you:

• Ground everything in your catalog. The Contextual Enrichment Engine reads a product set and derives eight sections of contextual rules (consumer criteria, use cases, purchase occasions, objections, and more). Every piece of content is generated against those rules, so tone and claims stay consistent.
• Generate PDP content. Product descriptions, meta tags, JSON-LD schema, IRL scenario cards, and internal linking suggestions.
• Produce channel-ready feeds. Google Shopping, Agentic Commerce, Microsoft, and Shopify field sets.
• Work wherever you are. The dashboard, the REST API, the SDK, the CLI, or an AI assistant through the MCP server.

Your first five minutes

1. Sign in at https://ace.authoritas.com.

2. Create an API key under Settings, Developer console, Keys. Start with an ace_test_ key: it is free and capped by a monthly quota. Copy it now, because the full value is shown only once. See API Keys.

3. Confirm the service is up. No key needed:

   curl https://ace.authoritas.com/api/v1/health

4. Check what your key can spend:

   curl https://ace.authoritas.com/api/v1/usage \
     -H "Authorization: Bearer $ACE_API_KEY"

5. Run your first enrichment. This generates a description and meta tags for one product:

   curl -X POST https://ace.authoritas.com/api/v1/enrichment/pipeline \
     -H "Authorization: Bearer $ACE_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "source": {
         "type": "inline",
         "products": [
           { "id": "sku-1", "title": "Merino base layer", "category": "Outdoor" }
         ]
       },
       "contentTypes": ["product-description", "meta-tags"]
     }'

   A small set comes back inline. A larger one returns 202 with a job id: poll it with GET /api/v1/jobs/{id}, or use webhooks.

For a fuller walkthrough see Enriching your first feed.

What you need

• An account in the app.
• An API key for programmatic access, with the scopes for what you plan to call. See API Keys.
• Credits for live enrichment. Test keys run free against a monthly quota instead. See Credits and usage.

Using the API

• Base URL: https://ace.authoritas.com/api/v1
• Auth: send your key as Authorization: Bearer <key> or X-API-Key: <key>
• OpenAPI spec: GET /api/v1/openapi returns the full spec in OpenAPI 3.0 format

Main entry points:

• Contextual Enrichment Engine: rules, content, and the full pipeline
• Jobs: track, page through, and cancel durable work
• ACE SDK: typed JavaScript and TypeScript client
• ACE CLI: the same endpoints from your terminal
• MCP Server: let Cursor, VS Code, or Claude call ACE directly
• API Reference: every endpoint, with schemas and a live request panel

App settings

• Settings, Developer console, Keys: create and manage API keys, scopes, and rate limits.
• Settings, Developer console, MCP: connect an MCP client and choose which tools are enabled for your project. See MCP Server.
• Settings, Developer console, Usage and Logs: request history and spend.

Common issues

• 401 Unauthorized: check the key is sent as Authorization: Bearer <key> or X-API-Key: <key>, and that it is active and unexpired.
• 403 Forbidden: the key is valid but lacks the scope for that endpoint or tool. The error names the scopes required. See API Keys.
• 402 Payment required: you are out of credits, or a test key has exhausted its monthly quota. Check GET /api/v1/usage.
• 429 Rate limit: your key has a requests per minute limit. Wait for Retry-After or raise the limit in Settings.
• MCP tool disabled: enable it for your project in Settings, Developer console, MCP. See MCP Server.

Anything else, see Troubleshooting.