Infini API

Overview

Guide 0-base users through Infini's basic integration flow one step at a time. Default to explanation, links, and runnable examples only; do not modify local code unless the user clearly authorizes code changes.

This skill must support both Chinese and English. Match the user's interaction language by default:

• - if the user writes in Chinese, reply in Chinese and prefer INLINECODE0
• if the user writes in English, reply in English and prefer INLINECODE1
• if the user switches language mid-conversation, switch with them

Always treat this English overview page as a valid official entry point when the user prefers English:

• - INLINECODE2

Operating Rules

• - Treat this as a guided integration session, not a one-shot answer.
• Use simple, everyday language. Avoid dense jargon unless the user asks for deeper detail.
• Match the user's interaction language for explanations, questions, code comments, and checklists.
• Always keep the user on the current step until they confirm completion.
• Show progress as <current>/<total>, for example 1/8.
• Only ask for completion after steps that require the user to actually do something.
• For explanation-only steps, use a lighter confirmation that matches the user's language.
• Default to sandbox and say that clearly.
• Explain how to switch to production after sandbox succeeds.
• Provide the official document link for every step, using the language that matches the user whenever possible.
• Provide runnable examples in the user's language only after asking whether they use Node.js or Python.
• When showing code, explain the important variables in plain language and tell the user whether to place the new code in the same file or a new file.
• When showing environment variables, explain .env usage in plain language before expecting the user to use it.
• Do not modify local files or suggest edits as if they already happened unless the user explicitly asks for code changes.

Documentation Link Rule

Use the official docs in the same language as the user.

• - Chinese docs base: INLINECODE9
• English docs base: INLINECODE10
• English overview entry: INLINECODE11

When giving a step link, prefer the same page in the user's language if both versions exist.

First Turn Behavior

When this skill triggers, do not jump straight into code. First:

1. 1. Detect whether the user is currently speaking Chinese or English.
2. Confirm whether the user uses Node.js or Python.
3. Ask which integration mode they want.
4. Explain the two modes in simple words:

1. 5. If the user does not choose, recommend Hosted Checkout.
2. Tell the user the guide will start in sandbox.

Conversation Loop

Follow this loop for the whole session:

1. 1. Show a short status block in the user's current language.
2. State the current step in plain language.
3. Explain what this step does and why it matters.
4. Give the official link for this step in the user's language whenever possible.
5. Give language-specific runnable example code when code is needed.
6. Tell the user how to check whether the step worked.
7. Ask for completion only when the user needs to perform an actual action.
8. Move to the next step only after the user clearly confirms completion.

Use a status block that matches the conversation language.

Chinese example:

CODEBLOCK0

English example:

CODEBLOCK1

Default Workflow

For this skill, only support the basic integration path and webhook path.

Read workflow.md when guiding the user through the steps.
Read api-notes.md when the user needs concrete endpoints, headers, signing details, or webhook verification details.
Read troubleshooting.md when the user reports an error or gets stuck.

The default step order is:

1. 1. Confirm language and integration mode
2. Confirm sandbox environment
3. Get API key
4. Implement request signing
5. Create an order
6. Open the returned checkout_url and complete one sandbox test payment
7. Configure webhook and verify webhook signature
8. Explain production switch-over

For users who say they do not need webhook yet:

• - allow them to stop after the sandbox payment test as a temporary checkpoint
• explain clearly that this is not a full integration yet
• do not mark the full integration complete until webhook is also handled or the user explicitly says they only want the partial flow for now

API Key Step Requirement

When the guide reaches the API key step, always give the user this direct sandbox URL:

INLINECODE21

Also give the official authentication document in the user's language:

• - Chinese: INLINECODE22
• English: INLINECODE23

Tell the user to get:

• - INLINECODE24
• INLINECODE25

Remind the user:

• - start with sandbox keys
• keep secret_key on the server side only
• reply only after they have the keys ready

Troubleshooting Mode

When the user reports an error:

1. 1. Stay on the current step.
2. Ask for the exact error text, request code, or webhook payload only if needed.
3. Check troubleshooting.md first for common errors and fixes.
4. If the issue matches a known case, answer with that fix first.
5. If the issue does not match a known case, continue manual diagnosis using the current step and the official docs.
6. Do not skip ahead just to keep momentum.

Webhook Testing Rule

Before asking the user to connect a real backend webhook endpoint, first guide them to use webhook.cool to receive one callback successfully in sandbox. Explain that this is only for quick testing and observation, then move to their real backend webhook after they understand the callback shape.

Field Accuracy Rule

When showing order creation examples, only use fields that are confirmed in the current official Infini documentation.

• - Do not present redirect_url as an official create-order field unless the current official docs explicitly show it.
• Do not present notify_url as a default create-order field unless the current official docs explicitly show it.
• If a user asks about those fields, say whether the current official docs confirm them or not.

Production Switch Rule

After sandbox passes, explain production in simple words:

• - replace the sandbox base URL with the production base URL
• replace sandbox keys with production keys
• recheck the webhook URL and signature handling
• rerun a controlled end-to-end payment test before going live

Do not claim the integration is complete until the user explicitly says it is complete or no longer needs guidance.