Use with AI coding tools

Company- and language-scoped context

These are real portal routes generated from published CMS content. llms.txt is a short index; llms-full.txt contains complete resolved documentation; openapi.json contains inline operation schemas and an OpenAPI 3.1 webhook; every page has a .md representation. Stay within the selected company/language rather than mixing providers. Record the actual document language when a translation falls back.

Claude, Codex, and Cursor

1. Claude: give a web-capable session the index URL; if web access is unavailable, download and attach the Markdown/OpenAPI files. Pasting a URL does not prove the assistant read it.
2. Codex: ask it to read llms.txt first, then fetch relevant .md pages and openapi.json with an allowed network tool. For offline work, provide downloaded files. Require generated code to be checked against schemas and missing facts to be reported.
3. Cursor: add the documentation URL as a Docs source if supported by your installed version, or download files into an approved context location and reference them in chat. Do not assume Cursor’s index is fresh; inspect the cited content and endpoints.
4. Ask for a plan before changing business behavior; resolve uncertainties with TMS, never let an assistant invent surchargeType, idempotency, or an SLA.
5. Exercise sandbox only with credentials kept outside prompts; compare COD, fees, label HTML, cancellation results, and duplicate webhook behavior.

Download context

# Set PORTAL_ORIGIN to the actual deployed portal origin, without a trailing slash.
curl --fail --show-error "${PORTAL_ORIGIN}/mfexpress/en/llms.txt"
curl --fail --show-error "${PORTAL_ORIGIN}/mfexpress/en/openapi.json" --output cambodia-openapi.json
curl --fail --show-error "${PORTAL_ORIGIN}/mfexpress/en/create-order.md" --output create-order.md

Suggested prompt

Read /mfexpress/en/llms.txt, the relevant Markdown pages, and /mfexpress/en/openapi.json. Implement only the Cambodia TMS Partner API described there. Cite page paths and field names for important decisions. Disclose actual document language and all uncertainties. Do not invent surchargeType enums or txId server idempotency. Send moneyCollection separately during creation and check cod. Labels are HTML; status lookup has only three fields. Propose sandbox checks and identify missing inputs, but do not request tokens or customer data in chat. Do not call production.

Safety boundaries

Do not include real API_TOKEN, PARTNER_CODE, webhook tokens, personal addresses, phones, customer orders, or production data in prompts, public context files, or shared logs. Use synthetic examples and environment variables. AI is not authority for the provider contract; this OpenAPI is a bounded interpretation of the document, not a TMS-certified specification. Review source details before accepting generated code.