How an agent can pay for a prepaid top-up
Public, zero-auth payment offer for agents. Lists the payment methods an agent can top up its prepaid balance with (only methods whose rail is switched on), the smallest and largest agent top-up in whole øre, the terms a payer accepts by paying, and whether pay to get a key and pay per request are switched on. Every method carries a protocol field (mpp or x402), so a later protocol is appended without changing existing fields. While no agent rail is switched on, methods is empty and agent_payments_enabled is false; a human can still top up on the billing dashboard. The 402 INSUFFICIENT_CREDITS body carries the same method list as payment_offer while a rail is on. Served with Cache-Control no-store (the body reflects runtime switches) and a strong ETag honouring If-None-Match.
Request
- Base URL: https://www.apier.no
- URL: https://www.apier.no/api/v1/payments/options
- Auth: none required
Response
The current payment offer.
Example response
{
"_meta": {
"rulebook_version": "v1.0.0",
"source": "apier.no",
"data_source": "Brønnøysund Enhetsregisteret + Apier Universal Rulebook",
"schema_version": "1.0.0",
"legal_basis": "NLOD — public registry reuse",
"response_timestamp": "2026-04-24T12:00:00.000Z",
"response_hash": "sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
"source_snapshot_id": "brreg-2026-04-24T02:00:00.000Z",
"cost_nok": 0.5,
"wallet_remaining_nok": 9.5,
"spend_cap_remaining_nok": 12.5
}
}Changes
No recorded changes to this operation across all 1 revision of this API.