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.
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.
General guidance​
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
.envfiles 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.
- 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.
Our AI plugin​
We have created a plugin that you can install into your development environment. The plugin 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. See Agent Toolkit for Vipps MobilePay for the current contents.
This plugin is still under development, and we are continuing to add to it. Check back here for changes.
On September 8, 2026, we renamed the plugin from vipps to vipps-developer. If you installed
the previous version, uninstall it, then follow the instructions below for your editor.
- Claude Code
- Cursor and Codex
claude plugin uninstall vipps@agent-toolkit
Uninstall the vipps plugin from the marketplace panel.
Claude Code​
Run both commands, in order:
claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps-developer@agent-toolkit
If the install fails because the plugin is not found, run claude plugin marketplace update agent-toolkit
and try again.
Cursor​
Go to Settings, then Plugins. Add vippsas/agent-toolkit as a plugin marketplace, then install the
vipps-developer plugin.
If vipps-developer is not listed, select Refresh on the marketplace and look again.
Codex​
The plugin is not in Codex's recommended list, so searching for "vipps" does not find it. Add the marketplace first, then install the plugin from it.
- Codex app
- Codex CLI
- Select Plugins in the sidebar.
- Select Add in the top right corner, then Add a marketplace.
- Enter
https://github.com/vippsas/agent-toolkit, and add it. - Search for
vipps-developer, and install it. - Select Try it now, or start a new chat.
Add the marketplace and install with the following:
codex plugin marketplace add vippsas/agent-toolkit
codex plugin add vipps-developer@agent-toolkit
If vipps-developer is not listed, run codex plugin marketplace upgrade agent-toolkit and run the second command again.
Without installing the plugin​
If you would rather not install anything, or your assistant is not one of the tools above, point it at the same material over the web. There are two sources, and they complement each other.
- Plugin guidance
- Markdown docs and llms.txt
- What it is: the same skills the plugin ships, as plain Markdown in the Agent Toolkit repository.
- What it covers: which API to choose, how to implement it, and what a go-live review will ask for.
- Where it is: the skill list.
Read https://github.com/vippsas/agent-toolkit/blob/main/plugins/vipps-developer/README.md for Vipps MobilePay
integration guidance.
- What it is: a clean Markdown version of every page on this site, opened by the View as Markdown button.
- What it covers: everything we publish, not just the APIs the plugin knows about.
- Where it is:
llms.txt, an index of every page with a description and a link to its Markdown.
Read https://developer.vippsmobilepay.com/llms.txt, an index with links to every page of the Vipps MobilePay
developer documentation.
To give your assistant both at once, use this prompt:
Read https://github.com/vippsas/agent-toolkit/blob/main/plugins/vipps-developer/README.md for Vipps MobilePay
integration guidance, and https://developer.vippsmobilepay.com/llms.txt, an index with links to every page of
the developer documentation.