---
title: "Why don't AI coding tools like REST?"
slug: "why-dont-ai-coding-tools-like-rest"
date: 2026-04-28
category: community
tags: []
language: en
sources_count: 1
featured: false
publisher: AInauten News
url: https://news.ainauten.com/en/story/why-dont-ai-coding-tools-like-rest
---

# Why don't AI coding tools like REST?

**Published**: 2026-04-28 | **Category**: community | **Sources**: 1

---

## TL;DR

A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?

---

## Summary

A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions? Is this a deliberate model choice, a token-efficiency artifact, or just a side effect of training data? Better prompting can steer the output, but the pattern is consistent enough to suggest something deeper.

---

## Why it matters

A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?

---

## Key Points

- A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?
- Is this a deliberate model choice, a token-efficiency artifact, or just a side effect of training data?
- Better prompting can steer the output, but the pattern is consistent enough to suggest something deeper.

---

## Nauti's Take

Nauti finds the observation valid and useful: knowing the pattern lets you prompt explicitly for RESTful output and get cleaner APIs — that saves bandwidth and keeps endpoints readable. The catch: the post offers no real explanation, and without data it remains open whether the cause is token efficiency, training-data bias, or model preference. Valuable for API designers working with AI tools — less relevant for teams already comfortable with RPC-style endpoints.

---


## FAQ

**Q:** What is Why don't AI coding tools like REST? about?

**A:** A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?

**Q:** Why does it matter?

**A:** A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?

**Q:** What are the key takeaways?

**A:** A Hacker News post raises a sharp question: why do AI coding tools so often default to RPC-style POST endpoints, even when a simple GET would do, instead of following REST conventions?. Is this a deliberate model choice, a token-efficiency artifact, or just a side effect of training data?. Better prompting can steer the output, but the pattern is consistent enough to suggest something deeper.

---

## Related Topics

- —

---

## Sources

- [Why don't AI coding tools like REST?](https://news.ycombinator.com/item?id=47939342) - Hacker News AI

---

## About This Article

This article is a synthesis of 1 sources, curated and summarized by AInauten News. We aggregate AI news from trusted sources and provide bilingual (German/English) coverage.

**Publisher**: [AInauten](https://www.ainauten.com) | **Site**: [news.ainauten.com](https://news.ainauten.com)

---

*Last Updated: 2026-04-28*