Oyenza (trafik.live) and Luca Cada Lora: A Relay Is Still an API

This post is my technical analysis of public posts by @lucaxyzz (Luca Cada Lora) about Oyenza, the name trafik.live goes by. I am not a party to the thread. It accuses no one of a crime or a breach of terms, and it is my opinion, not a finding by any court or regulator. Source for observations: my passive look at trafik.live in a normal browser, 19 Nov 2026, 03.53 WIB.
Other posts in this series: a relay is still an API, the data openness spectrum, Pasal 332 and the "tanpa hak" test, Live became Simulasi and the stronger answer. Earlier record: right of reply for Luca Cada Lora.
Luca Cada Lora, who posts as @lucaxyzz, said on 17 November 2026 that "trafik.live gada yg pake API, gue bikin relay" (nobody uses an API on trafik.live, I built a relay). Oyenza is the name trafik.live goes by. The claim has a correct half and an incomplete half, and I want to separate them.
What he wrote
- 17 Nov, 21.45 (last edited): "trafik.live gada yg pake API, gue bikin relay. Bahkan semuanya tertulis jelas pake simulasi." The post showed 37.8 thousand views.
- 17 Nov, 20.20: "Tinggal direverse atau nanya opencode jg beres dan ga butuh API".
- A reply: "Yaa api server sendiri" (yes, my own server's API).
The second sentence of the first post points a business owner or IT leader at the person who asked, whose question was why the answer was not simply that AI found the API.
What is right
Oyenza does not use an official public API from TransJakarta or DJKA, and a relay is a legitimate architecture pattern. One pull from upstream can serve many viewers, which lowers the load on the source.
What is incomplete
A relay is still an API. In my observation the browser only calls the trafik.live domain, for example /api/djka/manggarai-602/stream.m3u8 and its .ts segments, plus /api/stats. That is Oyenza's own API. Behind it, the server must call an upstream endpoint on behalf of every user. So there are two APIs in the chain: Oyenza's and the upstream one that reverse engineering found. "Nobody uses an API" and "my own server's API" correct each other. The fairest reading of the first sentence is that Oyenza does not use someone else's official API.
Observed and inferred
Observed (19 Nov, 03.53 WIB): every request goes to one origin, behind Cloudflare; versioned static data; the CCTV stream as HLS; /api/stats returns buses 0 with no-store; labels read "Bus 66 simulasi" and "Kereta 8 jadwal"; an attribution says "Buka di situs DJKA" and that it is not affiliated with TransJakarta.
Inferred, not proven: that the Oyenza server pulls from the DJKA station CCTV server (go2rtc) and re-serves it; that the fixed slug means an allowlist of cameras; that there is caching or transcoding.
The table Luca referred to, a reverse-engineered map of the Kemenhub CCTV site (variable stationListResult, 52 locations, 115 cameras), is something I have not re-verified against the original site.
A machine summary, used as context only
A reply from @grok summarised the thread: relay as a proxy so users do not hit upstream directly, simulation for lagging data, a plan to ask for official access, and a conclusion that it is not an official public API. That is a machine summary that I have not matched to every source post.
In short: a relay moves the API call to the server; it does not remove it.
Luca Cada Lora and Oyenza (trafik.live) can reply at admin@infraloka.co.id. A substantive response may be published alongside this article, and if reliable evidence shows a factual statement here is wrong, I will correct it promptly and note the change.
Published by Rahmat Wibowo, InfraLoka — infraloka.co.id
#Oyenza #TrafikLive #LucaCadaLora #FairRecord