Every listing from scratch
Same bedrooms, same square footage fields, and still an hour to write something that does not sound like every other listing.
For agents, brokerages and proptech
Listing copy that sells the light in the kitchen, lease abstracts that surface the break clause, follow-ups that land while the buyer is still excited. All from one endpoint.
from property notes to polished copy
key terms pulled into one page
drafted right after the viewing
The problem
Same bedrooms, same square footage fields, and still an hour to write something that does not sound like every other listing.
Rent reviews, break options and repair obligations buried across forty pages.
The viewing went well. The follow-up went out three days later.
Capabilities
Send features, neighbourhood notes and tone, get headline and body copy for each portal.
Extract parties, term, rent, review dates, break clauses and repair obligations as a structured summary.
Personalised notes after viewings and open houses, based on what the buyer actually said.
One authenticated endpoint with per-call pricing, so your platform knows the cost of every generated listing.
Identical prompts inside the cache window return instantly and are not billed.
The router picks the lowest-priced model with the capability you request.
Use cases
Variants sized for each portal and your own site.
A one-page abstract for asset managers and lenders.
Next-day emails that reference the viewing and next steps.
Local area overviews drafted from your own notes and data.
How it works
Paste your property notes and see the result and its price.
Call the endpoint with an API key from your workflow.
Track daily and month-to-date usage in the dashboard.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'Give it your agency's tone and a couple of past listings you love. It writes from what you send.
Send the lease text in the prompt and ask for the fields you need. Very long documents may need splitting into sections.
Treat output as a draft. Have a qualified person check abstracts and listing claims before they are used.
Each response shows its exact price. The catalog lists per-token prices for every model.
Write your next listing free. See the price before you scale.