ACE (Agentic Commerce Engine)

Introduction

Overview of the ACE (Agentic Commerce Engine) developer documentation and who it is for.

Welcome to the ACE (Agentic Commerce Engine) documentation.

Who this is for

Developers, integrators, and merchants who want to enrich product feeds, generate PDP content (descriptions, meta tags, JSON-LD, feed formats), and use ACE from the dashboard, the API, the CLI, or an AI assistant.

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

If you are using the ACE app rather than building against it, start with Using ACE.

How to use this site

  1. Start here: Getting Started covers what you need and your first call.
  2. Get a key: API Keys explains scopes, environments, and rate limits. Required for all programmatic access.
  3. Learn the engine: Contextual Enrichment Engine is the core of ACE and worth reading before you integrate.
  4. Pick your surface: the SDK for code, the CLI for the terminal, the MCP server for an AI assistant, or raw HTTP against the API Reference.

Start here


Guides


API

  • API Reference: every v1 endpoint with schemas and a live request panel.
  • Contextual Enrichment Engine: rules, content, and the full pipeline.
  • Jobs: track, page through, and cancel durable work.
  • Usage: credit balance, rate limit, and test quota.
  • OpenAPI: GET /api/v1/openapi returns the full spec.

Tools and integrations

  • ACE SDK: typed JavaScript and TypeScript client.
  • ACE CLI: the same endpoints from your terminal.
  • MCP Server: 36 tools for Cursor, VS Code, Claude Code, and other MCP clients.

  • Settings, Developer console, Keys: create and manage API keys.
  • Settings, Developer console, MCP: connect an MCP client and choose which tools are enabled.
  • CLI: npm install -g @authoritas-ace/ace-cli, then ace health, ace usage, ace pipeline. See CLI docs.
  • SDK: npm install @authoritas-ace/ace-sdk. See SDK docs.

On this page