Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices https://ift.tt/P4ySZJ6

Show HN: Hackney – Compare Uber, Lyft, Waymo, and Robotaxi Prices I created an app that compares real-time prices and wait times across Uber, Lyft, Waymo, Tesla Robotaxi, Curb, and Empower. It shows you all ride options in one list, then once you’re ready to book, it deeplinks you to the provider’s app with the route pre-filled. I reverse-engineered ride-hailing mobile apps to understand how they fetch prices from their servers. You sign in to my app with your ride-hailing accounts, and then my app requests live prices from the same APIs that ride-hailing apps use. Importantly, my app is built using an on-device approach: the app on your phone stores authentication tokens locally and sends network requests directly to each ride-hailing company’s servers. This keeps your accounts private. I wrote a blog post showing network requests sent by my app, which you can verify yourself: https://ift.tt/XRLkNuO This seems like an obvious app. Why doesn’t it already exist? That’s because most ride-hailing companies don’t offer public APIs for prices and wait times. Uber does offer one, but they prohibit using it for price comparison. When someone built a comparison app using the official API, Uber terminated their API access ( https://ift.tt/mWihprn ). There are apps today that don’t use official APIs, but they run your account tokens through their servers and send price requests server-side. To integrate a ride-hailing provider, my app sends network requests for sign-in, token refresh, ride prices, and ride history (to power a feature that shows you unified ride history across apps and how much you’ve saved on each ride). Some ride-hailing apps implement certificate pinning to prevent you from viewing their network requests, and some communicate with their server using Protobuf, a data format that doesn’t include the original field names. Building an app using this approach is technically complex, but it makes possible all sorts of useful products that couldn’t otherwise exist. The app is completely free. In the future, I may monetize through a subscription or partnerships with ride-hailing companies. I’d love to hear your feedback. You can download it today. iOS: https://ift.tt/uHeKw4f... Android: https://ift.tt/VahxDUj https://hackney.app/ July 13, 2026 at 04:47AM

Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop https://ift.tt/ecB24Fx

Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop https://ift.tt/7AtlB0v July 13, 2026 at 04:02AM

Show HN: A Sims-style house builder in the browser (Three.js, no back end) https://ift.tt/MzmaTSA

Show HN: A Sims-style house builder in the browser (Three.js, no back end) https://ift.tt/4hOepSc July 13, 2026 at 02:42AM

Show HN: DOM-docx – HTML to native, editable Word docs (MIT) https://ift.tt/MyEa3kB

Show HN: DOM-docx – HTML to native, editable Word docs (MIT) https://ift.tt/TLNW5wF July 13, 2026 at 01:51AM

Show HN: Skillscript – A declarative, sandboxed language for tool orchestration https://ift.tt/C016eYc

Show HN: Skillscript – A declarative, sandboxed language for tool orchestration Hi HN — I'm Scott. Skillscript is a small language I built to write what I want my local agent to actually do, in a form I can read and version, instead of hoping the model gets it right each time. The itch started with something small. I wanted my NanoClaw agent to run my morning brief the same way every day. Check overnight tickets, summarize the deploy pipeline, flag anything urgent. Every session, it would re-figure out how to do this from scratch, drift a little, and cost tokens for what's basically a fixed procedure. I could put it in a system prompt or an MD skill file, but those are still instructions the model reads and reasons about every time. And I wanted it to run autonomously and then hand it to the model to reason over the data. The second thing that pushed me: I wanted to use small local models for the cheap stuff. They're capable, but if you just hand them the wheel, they wander. What I wanted was a way for the frontier model (or me) to write a specific procedure and hand it to the local model to execute, not interpret. The skillscript is the program; the model is the runtime. Skillscript is that. A skillscript is a text file with named steps, variables, conditions, and calls out to tools (MCP connectors, a local model, and shell commands from an operator allowlist). It's deliberately minimal — no eval, no arbitrary imports, no subprocess, no unbounded loops. Bounded language, limited potential for damage. Everything a skillscript can do is in the file. You read it and know. Where it is: pre-1.0 (0.30), MCP-native, self-hosted. Rough edges I know about: first-run setup takes more steps than it should, some of the grammar is still moving, and the local model integration currently assumes Ollama. It works well enough that I use it every day, but I wouldn't necessarily call it production-ready. - Repo: [ https://ift.tt/CfmYpWA ]( https://ift.tt/CfmYpWA ) - Site: [ https://skillscript.ai ]( https://skillscript.ai ) - Docs: [ https://ift.tt/OWmpFGn ]( https://ift.tt/OWmpFGn ) - npm: `skillscript-runtime` I'd welcome critique on two things especially: the language design (is it too small? too big? wrong shape?) and the trust model around agent-authored skills. What would you want to see before you trusted this on your own machine? https://ift.tt/CfmYpWA July 12, 2026 at 03:34AM

Show HN: Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec https://ift.tt/K0E1Qwp

Show HN: Only 1 of 4,356 reachable MCP servers is ready for the 2026-07-28 spec https://ift.tt/FzfKhmZ July 12, 2026 at 03:21AM

Show HN: Fenzo – Build an interactive course on any topic https://ift.tt/dPOT1em

Show HN: Fenzo – Build an interactive course on any topic https://fenzo.ai/ July 12, 2026 at 12:09AM