# MercadoLibre Exodus Intelligence Feed (`khadinakbar/mercadolibre-exodus-intelligence-feed`) Actor

Authenticated MercadoLibre API feed for premium listing enrichment — descriptions, seller signals, and authorized Mexican vehicle compatibility. Requires owner OAuth token.

- **URL**: https://apify.com/khadinakbar/mercadolibre-exodus-intelligence-feed.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 premium enriched listings

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## MercadoLibre Exodus Intelligence Feed (Private)

This private integration is purpose-built for Exodus’s daily MercadoLibre Mexico
automotive-parts workflow. It replaces the slow browser verification loop with
bounded MercadoLibre API calls under an Exodus-managed OAuth token. It returns
one validated listing record with description and seller signals, or one
authorized vehicle-compatibility report per MercadoLibre user product.

### Use it for

- Enriching known MercadoLibre listing URLs with description and seller fields.
- Searching one LATAM marketplace through the authenticated API, then enriching
  up to 150 results in a bounded batch.
- Returning actual vehicle compatibility from the authorized
  `MLM-CARS_AND_VANS_FOR_COMPATIBILITIES` user-product endpoint.
- Verifying the Mexican compatibility domain without credentials as a fast
  health probe.

Do not use it as a general browser scraper, an unauthenticated listing API, or
as proof that a listing fits a particular vehicle without MercadoLibre’s
authorized compatibility response. The Actor never derives fitment from title,
attributes, or category alone.

### Required owner configuration

Set the Actor environment secret `MELI_ACCESS_TOKEN`. The token is never
accepted as a run input or written to logs. Listing enrichment returns
`CONFIG_ERROR` when the secret is absent and an honest upstream/config outcome
when MercadoLibre rejects it. An OAuth token with access to item descriptions
and user-product compatibility is required for the premium modes.

The default input is a no-secret compatibility-domain probe so automated health
checks can succeed without a customer token.

### Inputs

#### Enrich explicit listings

```json
{
  "mode": "listing_enrichment",
  "startUrls": [
    {
      "url": "https://articulo.mercadolibre.com.mx/MLM-1234567890-example-_JM"
    }
  ],
  "maxResults": 10,
  "apiConcurrency": 4
}
```

#### Search then enrich

```json
{
  "mode": "listing_enrichment",
  "country": "MX",
  "searchQuery": "filtro aire jetta",
  "maxResults": 150,
  "apiConcurrency": 4
}
```

#### Return authorized vehicle compatibility

```json
{
  "mode": "vehicle_compatibility",
  "startUrls": [
    {
      "url": "https://articulo.mercadolibre.com.mx/MLM-1234567890-example-_JM"
    }
  ],
  "maxResults": 150,
  "maxVehicleMatchesPerProduct": 50,
  "apiConcurrency": 4
}
```

If Exodus already stores MercadoLibre user-product IDs, provide `userProductIds`
instead of listing URLs to avoid the preliminary item lookup.

#### Discover the Mexico compatibility domain

```json
{
  "mode": "compatibility_domain",
  "compatibilityQuery": "camioneta"
}
```

### Output contract

`listing_enrichment` records contain `itemId`, `title`, `url`, `description`,
`sellerId`, `sellerReputation`, and `sellerLocation` when supplied by the
authenticated item API. A missing upstream description remains `null` with an
explicit warning; the Actor never synthesizes text or seller attributes.

`vehicle_compatibility` records contain only the exact entries MercadoLibre
returns for a user product under `MLM-CARS_AND_VANS_FOR_COMPATIBILITIES`, capped
at the requested per-product maximum. `compatibility_domain` records remain a
non-billable health probe; they do not represent a listing or vehicle match.

The Actor writes both `OUTPUT` and `RUN_SUMMARY` with one of `COMPLETE`,
`PARTIAL`, `VALID_EMPTY`, `INVALID_INPUT`, `UPSTREAM_FAILED`, or `CONFIG_ERROR`.

### Billing and cost boundary

One persisted premium listing costs `$0.02`; description and requested seller
fields are included in that same event, with no seller-detail surcharge. One
persisted vehicle-compatibility report costs `$0.01` per user product, covering
all returned matches up to the chosen cap. The non-billable health probe costs
only the `$0.00005` Actor start. Platform usage is paid by the caller through
Pay per event + usage.

At 150 enriched listings/day, event pricing is `$3.00/day`, or about `$90/month`
before the small start events and caller-paid platform usage. The API path avoids
residential-proxy usage. Compute and network usage are passed through to Exodus,
so the pricing retains a strong margin while giving the buyer a visible cost
boundary.

### Provenance and limitations

Descriptions use MercadoLibre’s item-description endpoint; seller fields are
read from the item response, so a separate seller-profile route is not needed
for Exodus’s requested fields. MercadoLibre compatibility rights and token scopes
remain the authority for item/user-product data. If a response is unavailable,
the Actor records `PARTIAL`, `VALID_EMPTY`, `UPSTREAM_FAILED`, or `CONFIG_ERROR`
rather than emitting invented compatibility.

Use the results only for legitimate ecommerce research and in accordance with
applicable law, marketplace terms, and your organization’s data-governance
requirements.

# Actor input Schema

## `mode` (type: `string`):

Choose compatibility\_domain for a no-secret Mexican domain health probe, listing\_enrichment for full descriptions and seller signals, or vehicle\_compatibility for authorized product-to-vehicle matches. The default health probe is not billed as a result. NOT a browser-scraping mode.

## `compatibilityQuery` (type: `string`):

Spanish search phrase used with MercadoLibre Mexico domain discovery. Example: 'camioneta'. The Actor emits only the proven MLM-CARS\_AND\_VANS\_FOR\_COMPATIBILITIES domain when it matches. Defaults to camioneta. NOT an item search or a vehicle fitment lookup.

## `startUrls` (type: `array`):

Direct public MercadoLibre or Mercado Livre listing URLs to enrich. Example: https://articulo.mercadolibre.com.mx/MLM-1234567890-example-\_JM. The Actor extracts canonical item IDs and fetches their API records. Use this or searchQuery in listing\_enrichment mode. NOT search or seller-profile URLs.

## `searchQuery` (type: `string`):

Keyword query submitted to the authenticated MercadoLibre site-search endpoint. Example: 'filtro aire jetta'. Use only in listing\_enrichment mode when no listing URLs are supplied. Results are capped by maxResults. NOT a compatibility-domain query.

## `country` (type: `string`):

Marketplace used for authenticated keyword search. Example: MX for Mexico. Listing URLs carry their own canonical item prefix; this setting only selects the search endpoint. Defaults to MX. NOT a proxy-country setting.

## `maxResults` (type: `integer`):

Hard cap on persisted listing or compatibility records. Example: 10 returns at most ten paid records. Defaults to 10 and caps at 150 so a daily job has a predictable budget. Each paid record is one billable event. NOT a page count.

## `apiConcurrency` (type: `integer`):

Maximum concurrent MercadoLibre API listing requests. Example: 4 runs four enrichment workers at once. Defaults to 4 and is limited to 6 to keep the owner token within a bounded request envelope. NOT browser or proxy concurrency.

## `userProductIds` (type: `array`):

Optional MercadoLibre user-product IDs for authorized vehicle compatibility. Example: MLMU123456. Use this in vehicle\_compatibility mode when Exodus already knows the product ID; listing URLs are resolved first otherwise. NOT seller IDs or vehicle IDs.

## `maxVehicleMatchesPerProduct` (type: `integer`):

Hard cap on compatibility entries returned for each MercadoLibre user product. Example: 50 retains the first fifty upstream matches. Defaults to 50 and caps at 100 to keep response size predictable. NOT a billable-event multiplier.

## Actor input object example

```json
{
  "mode": "compatibility_domain",
  "compatibilityQuery": "camioneta",
  "startUrls": [],
  "country": "MX",
  "maxResults": 10,
  "apiConcurrency": 4,
  "userProductIds": [],
  "maxVehicleMatchesPerProduct": 50
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "compatibility_domain",
    "compatibilityQuery": "camioneta",
    "maxResults": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("khadinakbar/mercadolibre-exodus-intelligence-feed").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "compatibility_domain",
    "compatibilityQuery": "camioneta",
    "maxResults": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/mercadolibre-exodus-intelligence-feed").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "compatibility_domain",
  "compatibilityQuery": "camioneta",
  "maxResults": 10
}' |
apify call khadinakbar/mercadolibre-exodus-intelligence-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khadinakbar/mercadolibre-exodus-intelligence-feed"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Aq9xDcsGbS9xwj1O5/builds/PFauehTm9UPbH9qHv/openapi.json