Use case
Developers building Persian-language AI agents need their agents to query products, prices and booking information on Iranian platforms such as Digikala, Snappfood and Jabama, handling platforms that expose no agent-facing interfaces, so the agent can call local service data and return results.
Writing one-off scrapers or scripts per platform, letting the agent answer generically and inaccurately, or temporarily gluing together generic web-scraping tools.
These Iranian platforms expose no agent-facing interfaces, so developers either write per-platform scrapers and adapters or let the agent answer generically and inaccurately; Toman-denominated prices, stock and booking status cannot be reliably obtained, and integration work is repetitive and fragile.
xOcto's call
Demand is evidenced
Trend: as model capability converges, what is scarce is agent-callable local service interfaces inside a specific language market; whoever standardises e-commerce, delivery and booking endpoints for non-English markets holds that market's agent entry point. Entry point: markets like Iran that mainstream tools ignore but where local platforms are dense, starting at the interface layer and later charging merchants for access or per-call revenue share; pricing and revenue share are not disclosed, and account and payment permissions need separate compliance review.
Reason to use it
Why users would choose it
Inference: versus building a scraper per platform, it unifies 385 tools across 24 services into agent-callable MCP interfaces and removes per-platform adaptation, so developers building Persian-language agent apps would adopt it first when integrating multiple local services; public material only shows repository stars, with no call volume, customer case or retention evidence, so long-term reliance cannot be confirmed.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: versus building a scraper per platform, it unifies 385 tools across 24 services into agent-callable MCP interfaces and removes per-platform adaptation, so developers building Persian-language agent apps would adopt it first when integrating multiple local services; public material only shows repository stars, with no call volume, customer case or retention evidence, so long-term reliance cannot be confirmed.
Entry and what to borrow
Trend: as model capability converges, what is scarce is agent-callable local service interfaces inside a specific language market; whoever standardises e-commerce, delivery and booking endpoints for non-English markets holds that market's agent entry point. Entry point: markets like Iran that mainstream tools ignore but where local platforms are dense, starting at the interface layer and later charging merchants for access or per-call revenue share; pricing and revenue share are not disclosed, and account and payment permissions need separate compliance review.