Agent Integration

Setup is required only once. After that, you do not need to find API paths, write JSON, or run API commands. Describe the task in Codex, Claude Code, or Cursor, and the Agent calls Ecommerce Data API and returns a clear text answer.

Help me set up Ecommerce Data API Agent integration on this computer. Complete the steps you can safely perform instead of only giving general instructions.

Goal: install the Ecommerce Data API CLI, Skill, and local MCP configuration for the available Codex, Claude Code, or Cursor client.
Documentation: https://ecommercedataapi.com/en/docs/launcher

Requirements:
1. Detect the operating system, Node.js version, and installed Codex, Claude Code, and Cursor clients. Windows requires Node.js 18 or newer.
2. Determine whether your terminal is actually running in my local user environment. If you are in an isolated sandbox without my local network or user-directory access, do not attempt the install. Tell me exactly which command to paste into my own Windows Terminal, PowerShell, or macOS/Linux Terminal.
3. When you can safely operate the local terminal, follow the documented installer flow with Manifest and SHA-256 validation. Install only detected or explicitly selected clients, and install each client separately when there is more than one.
4. Do not use unverified irm | iex or curl | bash shortcuts. Do not modify my project source code, system settings, or unrelated Agent configuration.
5. Never ask for, print, store, or append an API key in this chat. If I do not have a key, direct me to https://ecommercedataapi.com/en/settings/apikeys/create. When the installer requests it, let me enter it myself in the secure local prompt.
6. After installation, run ecomdata doctor and ecomdata mcp status to check the CLI, authentication, network, Catalog, and MCP configuration. If authentication is incomplete, explain how to run ecomdata login.
7. Finish with a concise checklist: operating system, connected Agents, Skill directories, MCP configuration status, verification results, and any manual steps I still need to perform.

Start in three steps

1. Prepare an API key

Create a key on the API key page if needed.

2. Choose an Agent and install

Choose the Agent you want to connect first. The installer adds the Skill and native MCP configuration by default, and installs the ecomdata CLI. The client identifier and Skill location are:

Use the command for your operating system. Run it in your own local terminal, not inside an AI chat sandbox.

macOS or Linux

Open Terminal. This example installs the Skill and local MCP for Codex:

curl -fsSL https://ecommercedataapi.com/install.sh | bash -s -- --yes --only codex

Replace codex with claude-code for Claude Code or cursor for Cursor. The installer asks for the API key through secure local input. Use --skip-mcp only when you deliberately want the Skill and CLI without MCP.

Windows PowerShell

Open Windows Terminal or PowerShell on your own computer. If the computer has only one supported Agent, paste this one-line quick install command. The installer detects Codex, Claude Code, or Cursor and requests the API key through secure local input:

$base='https://ecommercedataapi.com';$manifest=Invoke-RestMethod "$base/launcher/manifest.json";$installer=Join-Path $env:TEMP 'ecomdata-install.ps1';Invoke-WebRequest "$base/install.ps1" -OutFile $installer;if((Get-FileHash $installer -Algorithm SHA256).Hash.ToLowerInvariant() -ne $manifest.installers.windows_powershell.sha256){throw 'Installer checksum mismatch.'};& $installer -Yes

To target a particular Agent, or when the computer has more than one Agent, use the command below. This example installs Codex:

$base = 'https://ecommercedataapi.com'
$manifest = Invoke-RestMethod "$base/launcher/manifest.json"
$installer = Join-Path $env:TEMP 'ecomdata-install.ps1'
Invoke-WebRequest "$base/install.ps1" -OutFile $installer
if ((Get-FileHash $installer -Algorithm SHA256).Hash.ToLowerInvariant() -ne $manifest.installers.windows_powershell.sha256) { throw 'Installer checksum mismatch.' }
& powershell.exe -NoProfile -ExecutionPolicy Bypass -File $installer -Yes -Only codex

Replace codex with claude-code or cursor when appropriate. Add -SkipMcp only when you deliberately want the Skill and CLI without MCP. Windows does not require WSL. Node.js 18 or newer must be installed first.

The API key is requested through secure local input. It does not appear in the install command, shell history, or a project .env file.

3. Use the Skill and native MCP in your Agent

After installation, close and reopen the selected Agent, then start a new conversation:

To connect more than one Agent on the same computer, run the installer once for each target, for example --only codex and then --only claude-code. The clients use the same API key account and Credits, but each has its own Skill and MCP client configuration.

Choose the right integration

Ecommerce Data API has three separate integration surfaces:

Native MCP is local stdio only. There is no public remote /mcp endpoint to add to an Agent client. The MCP process uses the credential already configured for ecomdata; do not put an API key into an MCP URL or client configuration.

The installed native MCP exposes these four tools:

• ecommerce_api_search
• ecommerce_api_describe
• ecommerce_api_call
• ecommerce_account

4. Ask the Agent directly

Open Codex, Claude Code, or Cursor and enter a business question:

You:

Look up Amazon US product details for ASIN B08CK5Z5Q1. Return the brand, price,
rating, and review count, then tell me whether it deserves further research.

Agent:

Query complete:
- Product: ...
- Brand: ...
- Current price: ...
- Rating and review count: ...

Short assessment: ...

The actual fields and values come from the current API response. You can also request a more complete analysis:

Find the traffic keywords for Amazon US ASIN B08CK5Z5Q1. List the top 20 by
search volume, include the organic traffic ratio, and summarize the keywords
that deserve attention.

The Agent automatically:

1. Finds the most relevant API for the task.
2. Checks required inputs such as marketplace, ASIN, and keyword.
3. Calls the API.
4. Organizes the returned data into a readable answer.

When required information is missing, the Agent asks a short follow-up question, such as, "Which Amazon marketplace should I use?"

What to include in a request

In most cases, provide:

• Goal: what you want to find, compare, or analyze.
• Subject: an ASIN, keyword, category, or trademark.
• Marketplace: for example, Amazon US, UK, or JP.
• Output: for example, top 20, sorted by search volume, a table, or a short conclusion.

You do not need to know an API name, endpoint path, or JSON field.

Credits and confirmation

The Agent usually executes a single read-only request directly. Before a batch operation or a task that may consume more Credits, it explains the estimated calls and cost and waits for confirmation.

Troubleshooting

These commands are only needed for installation, authentication, or connection problems:

ecomdata login
ecomdata doctor
ecomdata update
ecomdata mcp serve
ecomdata mcp status
ecomdata mcp install --client codex
ecomdata mcp uninstall --client codex

• login: configure the API key again.
• doctor: check the account, balance, network, and Catalog.
• update: update the CLI or Skill.
• mcp serve: start the local stdio server. The configured client starts this automatically; run it manually only when diagnosing MCP startup.
• mcp status: show whether local MCP configuration is present for supported clients, without displaying the API key.
• mcp install --client <client>: add local MCP configuration after an installation that used --skip-mcp.
• mcp uninstall --client <client>: remove only that client's local MCP configuration; it does not remove the Skill or CLI.

If the current conversation does not detect Ecommerce Data API immediately after installation, run ecomdata mcp status, then start a new Agent conversation. Restart the client only if the new conversation still does not detect the Skill or MCP tools. Re-run ecomdata mcp install when status shows that a selected client is not configured. Replace codex with claude-code or cursor for those clients.

Catalog and regular API changes are available immediately without reinstalling. Run ecomdata update only when CLI or Skill behavior changes.