Metraipolis › archive › dc_8d6132990d23

Database-Augmented RAG for Automated Repair of REST API Misuses — arXiv:2608.29290

Source
arXiv (en)
Original
https://arxiv.org/abs/2608.29290
License (as archived)
CC0-1.0
Archived
2026-10-17T08:59:39.884Z
SHA-256 of the archived text
a52b106533991f15a6516a531845eb2037f6766567a0941df2788106c30d0e09
Stable URL of this page
https://metraipolis.com/documento/dc_8d6132990d23

How to cite

Database-Augmented RAG for Automated Repair of REST API Misuses — arXiv:2608.29290 — arXiv (en), https://arxiv.org/abs/2608.29290 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_8d6132990d23 (Metraipolis archive dc_8d6132990d23, sha256 a52b106533991f15a6516a531845eb2037f6766567a0941df2788106c30d0e09)
BibTeX
@misc{dc8d6132990d23,
  title = {Database-Augmented RAG for Automated Repair of REST API Misuses — arXiv:2608.29290},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2608.29290},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_8d6132990d23; sha256 a52b106533991f15a6516a531845eb2037f6766567a0941df2788106c30d0e09},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.29290. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Many Internet of Things (IoT) services provide Representational State Transfer (REST) APIs, which require client developers to implement applications that conform to the corresponding API specifications. When client programs contain API misuse, developers debug them based on error responses. However, such responses are often insufficient for identifying the root cause, requiring developers to repeatedly communicate with the server. Retrieval-Augmented Generation (RAG) is a promising approach for providing large language models (LLMs) with external knowledge. However, in automated repair of REST API misuses, it remains unclear how specifications should be stored in a RAG database. This study evaluates how different configurations for organizing API specifications affect RAG-based repair of REST API misuse. We constructed 11 RAG configurations with different database structures and compared their repair rates with a baseline method. For evaluation, we used REST API misuse cases collected from real-world repositories. The results show that, in the studied datasets, the baseline method achieved a repair rate of 54.3%, whereas a RAG-based method using four databases achieved a maximum repair rate of 88.6%. These results indicate that organizing specifications according to version and content type can be an effective design choice for RAG-based REST API misuse repair.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-01 in cs.SE).
Categorie arXiv: Information Retrieval (cs.IR) ; Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2608.29290 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-17T08:37:02.096Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-01?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).