Mercado Libre Product Research: product Selection API

Use Mercado Libre Product Research: product Selection API through Nexscope with documented parameters, structured results and API key authentication.

CostEstimated 10 credits / call

Try online

POST · https://api.nexscope.ai/mercado/productSelectionMCP · nexscope_data_mercado_product_selection

Mercado Libre Product Research

What this API does

Use Mercado Libre Product Research: product Selection API through Nexscope with documented parameters, structured results and API key authentication. The request accepts toolName, arguments. Its documented result includes errcode, errmsg, toolName, rawResponse, contentText, textParsedAsJson.

Mercado Libre Product Research: product Selection API API use cases

Find products matching a sourcing brief

To find products matching a sourcing brief, a marketplace analyst submits toolName and arguments to Mercado Libre Product Research: product Selection API. The returned errcode, errmsg, toolName help identify products matching the requested search criteria.

Compare a product search shortlist

A marketplace analyst uses Mercado Libre Product Research: product Selection API with toolName and arguments to compare a product search shortlist. The returned errcode, errmsg, toolName help compare candidates before requesting individual product details.

Collect candidates for a market review

For this workflow, a marketplace analyst calls Mercado Libre Product Research: product Selection API with toolName and arguments to collect candidates for a market review. The result helps choose products for a supplier or competitor review.

Mercado Libre Product Research: product Selection API API FAQ

What does the Mercado Libre Product Research: product Selection API API return?

Use Mercado Libre Product Research: product Selection API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes errcode, errmsg, toolName, rawResponse, contentText, textParsedAsJson. It corresponds to the supplied toolName, arguments. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Mercado Libre Product Research: product Selection API API cost?

The current documented cost is Estimated 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Mercado Libre Product Research: product Selection API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/mercado/productSelection with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_data_mercado_product_selection. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/mercado/productSelection

MCP method

nexscope_data_mercado_product_selection

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/mercado/productSelection

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/mercado/productSelection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "arguments": {
    "searchText": "Auriculares",
    "siteId": "MLM"
  },
  "toolName": "categorySearch"
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Mercado Libre Product Research

POSThttps://api.nexscope.ai/mercado/productSelection

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/mercado/productSelection`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`toolName`	`string`	required	One of 24 Meike multi-tool names, see table below.
`arguments`	`object`	required	The parameter object of the corresponding tool must be a JSON object and cannot be an array, string or number; the backend will remove `uId`, `uid`, `memberId` and crop empty values.

Code example

{
  "arguments": {
    "searchText": "Auriculares",
    "siteId": "MLM"
  },
  "toolName": "categorySearch"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (14 fields)

Name	Type	Required	Description
`code`	`string`	optional	Nexscope encapsulation layer status; `"200"` on success. May be omitted in case of business error.
`msg`	`string`	optional	Encapsulation layer message; `"ok"` on success.
`errcode`	`integer`	optional	Gateway status code; if successful, it is `200`, if there is a business error, it is non-`200`.
`errmsg`	`string`	optional	Gateway error or status message.
`type`	`string`	optional	Currently usually `rawMcpToolResult`.
`toolName`	`string`	optional	The name of the tool actually called.
`charged`	`boolean`	optional	Is there a fee for this tool?
`data`	`string/object/array`	optional	Business data unpacked from the MCP text content; most tools return a string.
`rawResponse`	`object`	optional	MCP `tools/call` Raw result; the current gateway usually returns an empty object.
`contentText`	`string`	optional	MCP text content The spliced original text.
`textParsedAsJson`	`boolean`	optional	Whether `contentText` is successfully parsed into JSON; it may also be `true` when the text is wrapped in a JSON string.
`total`	`integer`	optional	Returned when the number of records can be inferred by the backend; omitted when it cannot be inferred, and `null` is not returned.
`costToken`	`integer`	optional	The token cost of this call; the free tool is `0`, and the paid tool is currently `16000`.
`costTime`	`integer`	optional	The backend takes time in milliseconds.

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_mercado_product_selection",
    "arguments": {
      "arguments": {
        "searchText": "Auriculares",
        "siteId": "MLM"
      },
      "toolName": "categorySearch"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Estimated 10 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/mercado/productSelection

MCP method

nexscope_data_mercado_product_selection

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/mercado/productSelection \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "arguments": { "searchText": "Auriculares", "siteId": "MLM" }, "toolName": "categorySearch" }'

Response

No response yet. Run the request to see the response here.