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

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

Search then enrich

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

Return authorized vehicle compatibility

{
  "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

{
  "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.