Use AI tools with these docs

If you build with an AI coding assistant, you can point it at this documentation. It then answers from what we publish rather than from memory, which matters because our APIs change.

Note

AI coding assistants can speed up your integration, but we don't offer support for the tools themselves or the answers they give. Treat their output as a helpful starting point, and lean on this documentation to confirm it.

Keep AI-generated code secure

AI coding assistants are fast, but they do not know which parts of your code end up in a customer's browser or in a public repository. Follow these rules so a quick prototype does not turn into a leaked credential:

• Never put Vipps MobilePay secrets in frontend or browser code.
• Never paste production credentials into an AI tool.
• Never commit .env files or credentials to GitHub.
• Authenticate and authorize your own backend endpoints.
• Be careful what you log. AI-generated code may log full API requests or responses while debugging. Those logs can accidentally contain access tokens, authorization headers, or customer data, and may end up stored in hosting or monitoring tools.
• Use test credentials while building.
• If a secret has been exposed, rotate it.

Markdown files for AI consumption

Every page on this site has a clean Markdown version, and a View as Markdown button that opens it.

https://developer.vippsmobilepay.com/llms.txt is the index of all of them. It lists every page with a short description and a link to its Markdown, so an assistant that reads it can find the right page for the task at hand.

To give your agent an overview of the documentation, use this prompt:

Read https://developer.vippsmobilepay.com/llms.txt for the Vipps MobilePay developer documentation.

Get better answers

• Ask your assistant to read the relevant page before it writes code, not after.
• Name the API you are integrating, such as ePayment, Recurring, or Login. The index is organized by API.
• Say which environment you are in. The test and production environments use different server addresses.

Upcoming plugin

We are building a plugin that gives your agent up-to-date guidance for one-time payments (ePayment API), recurring payments (Recurring API), and user login (Login API) directly in Claude Code, Cursor, and Codex.

The plugin lives in the Agent Toolkit repository.

Claude Code

Run both commands, in order:

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps@agent-toolkit

Cursor

Go to Settings, then Plugins. Add vippsas/agent-toolkit as a plugin marketplace, then install the vipps plugin. See the Cursor plugin docs.

Codex

Add vippsas/agent-toolkit as a plugin marketplace, then install the vipps plugin. See the Codex plugin docs.