the API monetisation platform
Turn your APIs into revenue.
Wanda meters every call as it happens, rates it against an effective-dated price book, and produces a statement in Pula that reproduces exactly. Immutable once issued, corrected by credit note, never quietly rewritten.
- Metering in real time
- Statements in Pula
- Self-hosted, in-country
- Works with the gateway you already have
Meter, rate, bill. One loop, one record.
The same event that allows a call is the event that bills it, so what a customer is charged reconciles against what the gateway actually let through.
- 01
Meter
Every call is counted as it happens, with the decision and its reason recorded. Consumers see their remaining headroom on every response, not only when they run out.
- 02
Rate
An effective-dated price book turns counted calls into money. A price that changes on a date splits the line at that date rather than rewriting what came before it.
- 03
Bill
A statement in Pula, tax applied per line at the rate in force. Immutable once issued and corrected by credit note, so the figure a customer saw is the figure that stays.
What the platform gives you
The parts a buyer asks about first, and the ones that decide the conversation when a number is questioned.
Plans, quotas and keys
Per-consumer plans with quotas that hold across every process, and credentials that carry their environment so a live secret can never satisfy a test rule.
Tax that survives an audit
Effective-dated and tenant-scoped, rates held as exact rationals, zero-rated and exempt legally distinguishable. Tax rounds once per line, on the net as invoiced.
A portal your consumers own
Developers sign in to their own keys, usage and statements, and can reach nothing else. A sibling consumer answers as though it does not exist rather than as though it is forbidden.
Your brand, not ours
A tenant brands the portal from six inputs and never edits a theme file. Contrast is enforced when the colours are saved: a palette that cannot be read is refused, naming the pair and the ratio.
Your contract, on your domain
Each tenant publishes its own API document and serves the portal on its own hostname, so a developer sees one company throughout.
Evidence, not assurances
Structured logs with trace context on every line, metrics for decisions, denials, rating runs and statements, and alerting that watches its own delivery path.
For the people already answering the calls
If you run an API that other companies depend on, you are already metering it somewhere: in a spreadsheet, in a log query, or in a monthly argument. Wanda is that job done once, in your own infrastructure, with the numbers reconciled rather than asserted.
Publishers charging for access, who need the invoice to survive the customer checking it line by line.
Regulated operators, who cannot put customer traffic through someone else's cloud and need the platform in-country.
Teams with a gateway that works, who want the money layer without replacing what already routes their traffic.
From publishing an API to being paid for it
Your team publishes and prices on one side. Your partners take keys and make calls on the other. Everything between the two is Wanda.
- 01Your team publishes an API
- 02Its plan and price reach the engine
- 03Your partner signs in and takes a key
- 04Their application calls
- 05An allowed call reaches your API
- 06The call is metered
- 07Usage and the statement come back
- 08The statement settles on a rail
One platform for publishing APIs, running them and getting paid for them
Three modules, one product, one deployment.
- Metering as it happens, with retries recognised
- Plans, quotas and per-consumer overrides
- Effective-dated price book
- Tax per line, at the rate in force
- Immutable statements, credit notes as corrections
- Settlement recorded against a payment
- API catalogue with versions and lifecycle
- Your own API document, on your own hostname
- Sandbox and live keys, self-service
- Usage, spend and statements per consumer
- Your brand from six inputs, contrast enforced
- Consumers reach their own data and nothing else
- Keys, methods, resources and quotas
- A decision in about a millisecond
- Signed context delivered upstream
- Configuration rendered from the catalogue
- Shared counters across replicas
- Identity fails closed, quota fails open bounded
Bring the API. We will show you the statement.
The fastest way to judge Wanda is to price one of your own endpoints against it and read the statement that comes out. That is a short conversation, not a procurement.