Live data from Hacker News

Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

github.com

11–20 of 87 posts

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#11
Will this work for SSR applications? e.g. think old school net or jsp apps which make network requests then receive HTML which then needs to be parsed in order to understand the key pieces of information and then additional network requests?

I've found it relatively straight forward to reverse engineer SPA requests however with server side rendered apps, yow would your service handle that?

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#12

Will this work for SSR applications? e.g. think old school net or jsp apps which make network requests then receive HTML which then needs to be parsed in order to understand the key pieces of information and then additional network requests? I've found it relatively straight forward to reverse engineer SPA requests however with server side rendered apps, yow would your service handle that?

Would be cool to use a proxy to MITM to twiddle the bits (with its own API) if the use case isn't supported by a browser or robotic process automation driving the app's client side UX.

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#13

Will this work for SSR applications? e.g. think old school net or jsp apps which make network requests then receive HTML which then needs to be parsed in order to understand the key pieces of information and then additional network requests? I've found it relatively straight forward to reverse engineer SPA requests however with server side rendered apps, yow would your service handle that?

Would be cool to use a proxy to MITM to twiddle the bits (with its own API) if the use case isn't supported by a browser or robotic process automation driving the app's client side UX.

I was talking about web apps. But yeah, for old school desktop apps or windows native proxy MITM works

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#14

Will this work for SSR applications? e.g. think old school net or jsp apps which make network requests then receive HTML which then needs to be parsed in order to understand the key pieces of information and then additional network requests? I've found it relatively straight forward to reverse engineer SPA requests however with server side rendered apps, yow would your service handle that?

Good question. Finding the request that's responsible for the action you want will be a bit trickier for SSR, but it's still possible for most cases. It auto-generates regex (for now) to parse out needed info out of the html template.

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#16
Nice work, congrats! How do you deal with security related stuff like recaptcha, signed requests and so on?

Do you also support internal APIs of mobile applications? If so, how do you deal with AppCheck / PlayIntegrity / Android Key Attestation / Apple App Attest?

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#17
post #9

I just noticed over the weekend new Claude agreed to reverse engineer a graphql server with introspection turned off, something Im pretty sure it would have refused for ethical reasons before the new version it kept writing scripts, i would paste the output, and it would keep going, until it was able to create its own working discount code on an actual retail website The only issue with these kinds of things is break…

We are working on a way to auto-patch internal APIs that change by having another agent trigger the requests.

Regarding the legality aspects — really appreciate you mentioning this — we’ve put a lot of thought into these issues, and it’s something we’re continually working on and refining.

Ultimately, our goal is to allow each developer to make their own informed decision regarding the policies of the platforms that they're working with. There are situations where unofficial APIs can be both legal and beneficial, such as when they're used to access data that the end user rightfully owns and controls.

For our hosted service, we aim to balance serving legitimate data needs with safeguarding against bad actors, and we’re fully aware this can be a tricky line to navigate. What this looks like in reality would be to prioritize use cases where the end-user truly owns the data. But we know this is not always black-and-white, and will come up with the right legal language as you recommended. What does help our case is that many companies are making unofficial APIs for their own purposes, so there are legal precedents that we can refer to.

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#18
post #15

This is really awesome. There's several platforms that intentionally gate keep their API and it makes really annoying to build integrations with them. How do you go about these platforms and not breaking their TOS?

I don't think it really matters to them. As a provider giving access to these platforms, they're not the user (and they didn't agree to the terms). the end user did, so it's on them to decide whether they risk getting terminated or whatnot

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#19
post #15

This is really awesome. There's several platforms that intentionally gate keep their API and it makes really annoying to build integrations with them. How do you go about these platforms and not breaking their TOS?

Thank you! There are definitely platforms that intentionally gate-keep their APIs. A good example is LinkedIn, which many companies still try to force-build their own integrations with. Our goal is to allow each developer to make their own informed decision regarding the policies of the platforms that they're working with. For our hosted service, we want to prioritize use cases where the end-user truly owns the data. We can also refer to legal precedent cases where many other companies make unofficial APIs.

Re: Launch HN: Integuru (YC W24) – Reverse-engineer internal APIs using LLMs

#20

Nice work, congrats! How do you deal with security related stuff like recaptcha, signed requests and so on? Do you also support internal APIs of mobile applications? If so, how do you deal with AppCheck / PlayIntegrity / Android Key Attestation / Apple App Attest?

Thank you! Integuru itself doesn't handle recaptchas and signed requests, but we have a hosted solution where we use third-party services to handle recaptchas and manually create integrations for handling signed requests.

We do not directly support APIs for mobile applications; however, if you use MITM software and get all the network requests into a .har file, Integuru should work as expected. We do not handle AppCheck ATM at the moment unfortunately.

Post reply on HN