---
title: "OpenSanctions API credit bundles"
url: "https://www.opensanctions.org/changelog/51/"
id: "51"
date_created: "2026-09-24T06:58:32.012Z"
date_effective: "2026-09-24"
breaking: false
categories: ["Hosted API"]
---

# OpenSanctions API credit bundles

We're adding a new billing model to the OpenSanctions API: prepaid credit bundles, which you buy in the [customer portal](/account/). Existing customers stay on their current billing unless explicitly migrated. To move over sooner, contact [the support team](/support/). Your API key, endpoints and integration stay the same after migrating, so there is no code to change. Larger bundles cost less per screening query: you pay less by committing to more, there is no usage bill at the end of the month. In effect, you can manage your API spend precisely. The on-premise API (yente) is not affected. Credit bundles will eventually be the default way for new customers to use the OpenSanctions API.

| Bundle price | Credits | Price per screening query |
|---:|---:|---:|
| €50 | 500 | €0.10 |
| €400 | 5,000 | €0.08 |
| €2,000 | 30,000 | €0.067 |
| €5,000 | 100,000 | €0.05 |
| €15,000 | 500,000 | €0.03 |

Prices exclude applicable tax. Credits are valid for one year from purchase. Only `/match` and `/search` consume credits: each query in a `/match` request uses one credit, so a batch of 100 queries uses 100 credits, and each `/search` request uses one credit. Calls to `/entities` and `/statements` remain free. You receive an email when you have used 50% and 80% of a bundle, so you can keep track of consumption. If you want screening to continue without interruption, turn on auto-recharge in the portal: a new bundle of the size you choose is then bought automatically when your balance runs low.

For more on how requests are metered, see the [API FAQ](/docs/api/faq/).