Arqdia v1.1.3.The Direct Booking sprint —new agents, billing & fixes.
See where OTA commission leaks — and win it back direct.
The flagship of the 28 Jun–5 Jul sprint. ARIA's eighth agent watches your portfolio for commission leakage and direct-booking opportunities, refreshing a DirectBookingState every 6 hours with dependency tiers.
Four detectors ship in this release: commission leakage, repeat-guest OTA leak, rate-parity violation, and direct-share decline — each surfaced as a Decision Card, backed by tests + CloudWatch metrics.

Charge, sell chat tokens, and invoice — in-app.
A full billing loop: pay Arqdia inside the product via Paddle, and buy token packs for ArqChat that raise your allowed usage automatically.
Every transaction shows up as an invoice in Arqdia-admin, with revenue reporting so you can see what's coming in.

Sharper rates, more reliable rules.
New dynamic-pricing algorithms improve rate recommendations, and ARIA can now drive automations as part of a resolution.
The automation engine got a round of fixes so rules run predictably.

Steadier under load, tighter integrations.
Integration execution is now correctly scoped per-user, and in-app plus AWS rate limiting protect the platform under load.
Behind the scenes: a secrets vault for the manager-web frontend, a Kafka drift audit (orphaned topics / partition mismatches), pre-prod pipelines, and QA-pipeline improvements.

Inactive listings stopped generating noise.
Guesty lets you mark a property inactive, but the sync was still pulling those units in — so ARIA and the agents behind the scenes generated insights for listings you no longer use.
Inactive Guesty properties are now excluded end-to-end: they don't sync, and no agent produces insights for them.

The numbers now add up, per door.
Financial figures shown at the individual unit (per-door) level were miscalculated in some cases.
The per-unit calculations have been fixed so revenue and cost figures are accurate for every unit.

Authenticated CRUD with correct responses.
The Policies API wasn't behaving correctly under authentication and validation.
Listing returns the full set of policies, creating with an empty body is rejected cleanly (400/422), and updating or deleting an unknown policy returns a proper not-found (404) — with the whole CRUD surface authenticated.

Google Maps and image upload work again.
Two smaller production issues are resolved: the Google Maps integration and uploading images from the workspace.
Maps render correctly and workspace image uploads succeed reliably.

Beta access · v1.1.3

Direct Booking Agent (#8)
See where OTA commission leaks — and win it back direct.
Ready to try v1.1.3?
Get in touch and we'll walk you through v1.1.3 on a real property in your portfolio — including a live ARIA Decision Card.