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.

Start in three steps

1. Prepare an API key

Create a key on the API key page if needed.

2. Install and sign in

Run this command in a terminal:

curl -fsSL https://ecommercedataapi.com/install.sh | bash

The installer detects Codex, Claude Code, and Cursor, then requests your API key through secure local input. The key does not appear in the install command, shell history, or a project .env file.

3. 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

• login: configure the API key again.
• doctor: check the account, balance, network, and Catalog.
• update: update the CLI or Skill.

If the current conversation does not detect Ecommerce Data API immediately after installation, start a new Agent conversation. Restart the client only if the new conversation still does not detect it.

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