---
title: Welila
description: Welila keeps your API's price per call right where agents read it. When your pricing page and your docs disagree, you settle it in one tap and the record keeps the answer.
canonical: https://welila.com
---

# Your price per call, where agents read it

Not this promise: agent-ready docs in one click, guaranteed. That is the whole promise. Below, the pricing page and the docs disagree on the price of an address lookup at Larchpost, Welila's sample API. Each part of the promise is kept as it happens.

## One price, settled

Welila asks the seller which is right. Your docs now show your address lookup price as £0.002 a call. Your pricing page says £0.004 a call. That night a buyer tells an agent "Look up these 2,000 addresses on Larchpost. Keep it under £5." and the agent answers "Larchpost's docs say £0.002 a call, so 2,000 lookups come to £4.00. Starting now." The seller answers in one tap. A week later the agent says "At £0.004 a call, 2,000 lookups come to £8.00, over your £5 limit, so I haven't started. Larchpost's Welila page lists an address lookup at £0.004 a call, confirmed by the seller on 30 August 2026."

- You decide which side is wrong. An audit holds the pricing page against the docs, and you settle what disagrees. Every fact's history shows who settled it and when.
- No promises about agent traffic. Welila does not sell calls or send agents your way. It works on the part it can fix, which is whether the price an agent reads is the one you charge.
- No quiet edits to your history. Your answer is written to the record with the time. A correction adds a new line, and nothing above it ever changes.
- Your price per call, where agents read it. The answer reached Welila's page and its files within five minutes, in a line an agent can quote.

An illustration of one finding from an audit. Agents answer in their own words, and the check that reads an API on its own isn't built yet. Larchpost is Welila's sample API, not a customer.

## Where the promise stops

- No call you didn't allow. Welila reads the public pricing page and docs. An audit calls the API only with the key and the cap you agree, against a sandbox where one exists.
- No guessing at your bill. A price is checked against the billing evidence you supply. Welila never works out what you charge from the outside.
- Nothing charged yet. Welila is in a closed beta and isn't taking payment. The first audits run as conversations with the sellers who ask for one.

## An audit, then rechecks

- An API audit, £750, once, for one version of your API. Up to ten operations that matter to you, held against your OpenAPI document, your docs and the live API. Each disagreement comes with its evidence, and you confirm which side is right.
- Rechecks, £250 a month, after an audit. The same operations checked again each month, so a change to your docs or your API shows before an agent trips on it.

See every price Welila sells on the pricing page at https://welila.com/pricing.

## Hold Welila to it

Compare each line above with the controls that run today at https://welila.com/trust. Tell us about your API next, and which prices an agent should never get wrong.

Duncan Forbes, who founded Welila, reads every message to hello@welila.com and answers it. [Talk to us](https://welila.com/contact).

Run a place people visit? See the places page at https://welila.com/places.

## Read it as a machine

- The open API is documented at /openapi.json.
- The tool is at /mcp with the same facts.
- The catalogue is at /.well-known/ard.json.
- Ask any page for text/markdown, or add .md to its path.