CLI Market

3,760 retailers, one API for AI agents

Open Source

Developer Tools

Artificial Intelligence

GitHub

Visit WebsiteSee on Product HuntGithub ⧉

Thanks again for all the support on CLI Market 🙌

Quick Day 2 update from the team:

In the first 48 hours, we’ve been focused on 3 things:

1) making onboarding faster,

2) improving search/compare reliability, and

3) keeping checkout safe with explicit human confirmation.

CLI Market gives AI agents one MCP interface to search, compare, and buy across 3,760+ retailers in 67 countries.

If you’ve tried it already, I’d love your blunt feedback:

• Where did setup feel slow/confusing?

• Which use case should we prioritize next?

• What’s missing for production use in your workflow?

We’re shipping improvements daily and replying to every comment.

Project: https://cli-market.dev

GitHub: https://github.com/Treevu-ai/cli-market-world

If you want, I can also draft a shorter, more casual version (PH-native tone) and a more technical version for builder audiences.

CLI Market is now on the official MCP Registry:

io.github.Treevu-ai/cli-market

12 tools. 3,760 retailers. 67 countries.

our agent can search, compare, and buy — autonomously,

at least you say no.

pip install cli-market

What "registered" means:

1. the MCP Registry validated ownership (via PyPI README annotation),

2. schema compliance (OpenAPI validator), &

3. package integrity (version-locked PyPI distribution).

The 12 tools compose. market_compare normalizes SKUs across

retailers before returning prices.

market_checkout chains

validation → stock → payment → confirmation.

market_ask walks natural language to purchase in one call.

Happy to answer questions about the registration process

or the tool architecture.

🎯 Why now?

AI agents can't buy across LATAM retail. APIs require

auth-per-retailer, no unified cart, no comparison.

Example: Agent scoring PyME creditworthiness by comparing

supplier prices across 50 retailers — manually impossible,

but CLI Market does it in 12 lines:

market search "arroz" --country PE

market compare "arroz"

market add 1 --qty 100

market checkout --payment bank_transfer

Without CLI-MARKET: 50 separate API integrations + auth

+ parsing + error handling = 2-3 weeks engineering.

With CLI-MARKET: one SDK call.

Repo: github.com/Treevu-ai/cli-market-world

The cross-retailer checkout orchestration is the capability that immediately made me pause. If an agent can trigger checkout across multiple retailers via MCP, what does the authorization model look like in practice? Specifically, is the checkout tool designed to require an explicit human-confirmation step before execution, or can an agent call it autonomously based on a user intent signal?

Interesting angle - most "AI agent + commerce" plays go through Shopify/Amazon APIs. VTEX-first via CLI is a sharper wedge for LatAm. Question: are the 12 MCP tools wrapping the same REST endpoints, or do they expose composite operations (e.g., compare-then-buy as one tool call)?