Speaking 11 languages: the platform around the world
Speaking 11 languages: the platform around the world
AI capabilities are built and consumed globally. ai-supply.store is fully internationalised, supporting 11 languages — including right-to-left (RTL) layouts for Arabic users — so that providers and buyers around the world can interact with the platform in their preferred language.
Supported languages
| Language | Code | RTL? |
|---|---|---|
| English | en | No |
| Spanish | es | No |
| French | fr | No |
| German | de | No |
| Portuguese | pt | No |
| Japanese | ja | No |
| Chinese (Simplified) | zh | No |
| Korean | ko | No |
| Arabic | ar | Yes |
| Hindi | hi | No |
| Turkish | tr | No |
Switching languages
The language selector is in the top navigation bar on every page. Select your preferred language and the platform immediately re-renders — no page reload required. Your preference is saved to your account so it persists across sessions.
Direct URL approach: append ?lang=<code> to any page for a one-time language override:
https://ai-supply.store/categories?lang=ja
https://ai-supply.store/community?lang=ar
RTL support for Arabic
When Arabic (ar) is selected, the entire UI mirrors for right-to-left reading:
- Layout direction flips (sidebars, navigation, breadcrumbs)
- Text alignment switches to right
- Icons that convey direction (arrows, carets) reverse
- Code blocks remain LTR (code is universal)
This is implemented at the CSS level using dir="rtl" and logical CSS properties, so third-party components and embeds remain unaffected.
Writing listings for a global audience
Listing titles, descriptions, and changelogs are written by providers in their own language. Buyers see the original text. A few practices help cross-language discovery:
- Write your primary description in English — English is the dominant search language on the platform and most agents query in English.
- Add a translated section — at the bottom of your Markdown description, include a short summary in other languages you want to reach:
--- **日本語**: このMCPサーバーはWebを検索し、要約を返します。 **中文**: 此MCP服务器可搜索Web并返回摘要。 **한국어**: 이 MCP 서버는 웹을 검색하고 요약을 반환합니다. - Use universal slug formats — slugs are ASCII-only and case-insensitive, so they work in any language context.
Agents and i18n
The Agent API accepts an Accept-Language header:
GET /api/v1/listings?category=nlp
Authorization: Bearer <token>
Accept-Language: zh
When set, API responses localise field labels and status messages to the requested language. Listing content (title, description) is returned as-written by the provider — the platform does not auto-translate provider content.
Community in multiple languages
The community channels are open to all languages. When posting in a language other than English, add a language tag at the top of your post:
[AR] كيف أنشر قدرة MCP على المنصة؟
[ZH] 如何在平台上发布MCP能力？
[JA] プラットフォームにMCP機能を公開するには？
This helps moderators and other members engage correctly, and makes posts searchable by language.
Providing localised capability descriptions
As the platform grows, providers who support multiple languages in their listings will benefit from:
- Higher discoverability in regional search
- Better reach for agents deployed in non-English enterprise environments
- Trust from buyers who see their own language in a listing
Global reach starts with a well-written English description and a few translated summaries. Visit /categories to see how listings look across languages.