← back to landing

Three ways to adopt

For solo devs, agencies, SaaS hosts, or marketplace operators — from zero-friction try-before-you-commit through to a formal commercial integration. Every path is reversible.

path A

Try

No commitment. ~5 minutes.
The default path for most adopters.  You want to use the toolkit in your own product. Solo dev, agency, or SaaS.
  1. 1
    Install
    pnpm add @ar-agents/mercadolibre
  2. 2
    Wire to your AI agent
    import { MeliClient } from "@ar-agents/mercadolibre"; import { meliTools } from "@ar-agents/mercadolibre/ai-sdk"; const client = new MeliClient({ auth: { kind: "bearer", accessToken: process.env.MELI_ACCESS_TOKEN! }, }); const tools = meliTools(client, { siteId: "MLA", sellerId: 12345, });
  3. 3
    Optional: read the cookbook
    12 production recipes covering OAuth, daily-triage agents, webhooks, HITL, ACP feeds, and more → cookbook/.
obligations + reversibility
  • MIT license — keep the copyright notice if you redistribute.
  • No data collection — the lib runs in your runtime.
  • No SLA — best-effort community support via GitHub issues.
Reversibility: Total. Just `pnpm remove`.
path B

Partner

Co-maintain, formal contributor relationship. ~30 days.
Right when MELI / a marketplace wants to formalize without IP transfer.  You're an established team that wants influence on the roadmap, public co-credit, or a formal seat at the maintenance table.
  1. 1
    Open 3+ substantive PRs
    Bug fixes, new test coverage, new cookbook recipes, or documentation improvements. Substance > volume.
  2. 2
    Email naza@helloastro.co with subject [co-maintain]
    Include links to your PRs and a 1-line statement of intent. Response in 7 days.
  3. 3
    30-day trial
    Triage rights on the repo. Joint decision-making on PRs. End of trial = permanent maintainer slot if both sides agree.
obligations + reversibility
  • MIT license preserved.
  • Co-maintainer commits to ~5 hrs/week minimum during active periods.
  • Joint decisions on roadmap, BREAKING changes, version cuts.
  • Co-maintained line in README + CHANGELOG.
  • No compensation, no contract — pure technical reputation trade.
Reversibility: Either side can walk with 30 days notice. Repo stays MIT.
path C

License

Commercial integration. Terms negotiable.
Right when an enterprise needs SLA, indemnification, or IP control.  You're a marketplace, payments processor, or large SaaS that wants legal certainty + co-marking + a contracted handoff.
  1. 1
    Email naza@helloastro.co with subject [vendor]
    Tell us your jurisdiction, the scope (exclusive vs non-exclusive), and any specific clauses you need (indemnification, audit rights, escrow, etc.). Response in 72 hours.
  2. 2
    Diligence call
    60 minutes to walk through architecture, supply chain, data privacy, security posture. Same answers as on /operated-by, just narrated.
  3. 3
    Term sheet
    We use a simple template based on the standards of the OSS community (e.g., Sentry-style fair source, dual MIT + commercial). Counter-proposals welcome. Closing target: ~30-45 days from intent.
obligations + reversibility
  • Public package may be sunset, deprecated, or co-maintained — your call.
  • IP assignment depends on terms (full transfer / exclusive / non-exclusive).
  • 30-90 day handoff with author providing technical advisory.
  • Insurance / E&O coverage available via a third-party endorser if required.
Reversibility: Terms-dependent. Default term sheet includes a fork-back clause if maintenance lapses.

For all three paths, the technical surface is identical — same package, same tests, same vendor questionnaire on /operated-by. What changes is the legal envelope around it.