Listing Generator
Enter property data, get a listing. No template, no snippet library, no code.
What the Generator Does
You fill in a form with the data you're already capturing anyway: property type, location, area, rooms, year built, price, features, and the mandatory disclosures from the energy certificate. You also choose who the text is for and what tone it should be written in.
What comes back is a complete listing: headline, short teaser for the results list, property description, location, features, the mandatory disclosures as flowing text, a suitability note, and a short social-media snippet. All in English, ready to use or edit further.
Nothing Is Invented
The generator works exclusively with what you entered. If a field is missing, it simply doesn't appear in the text - instead of making up a feature that isn't there.
Disclosures Stay Verbatim
The figures from the energy certificate and the commission disclosure are carried over unchanged, never rounded and never reworded.
Wording That Holds Up
The audience description covers what a property suits - not who should live there. That keeps the text free of wording that could read as discriminatory.
Three Steps to a Finished Text
- Enter property data. A sample property is pre-filled so you can see the flow right away.
- Choose the audience. Target audience, tone and length determine how the text sounds and how long it is.
- Generate. Within a few seconds the listing is ready - with a button that copies it to the clipboard as Markdown.
If you need the same flow programmatically, find it in the Create Listing API and the guide From Property to Listing.
Access: You need your API key to make the call. The form asks for it, uses it only for that one call, and never stores or logs it. To learn how to generate a key, see Authentication.
Why It Runs Through the Gateway
Between the form and the language model sits the Kong AI Gateway. It handles, in one place, what every application would otherwise have to solve on its own:
| Task | Where it's handled |
|---|---|
| Provider and model choice | at the gateway - switching providers changes nothing in the form |
| Access control | at the gateway, not in the application |
| Usage and cost | the gateway logs what was consumed, per call and per key |
| Protection against unwanted input | prompt guard at the gateway |
| Lowering response times | semantic caching for recurring requests |
The generator itself doesn't know a provider key. It knows an address.