Đại Lý Liên Tục Nói Dối Tôi. Cho Đến Khi Tôi Dùng Trình Gỡ Lỗi AI Agent Apidog.
The article discusses the author's experience debugging an AI agent using Apidog's AI Agent Debugger. Initially, the agent incorrectly reported response times due to a misunderstanding of units. After clarifying the response schema and adjusting the system prompt, the agent provided accurate results.
- ▪The AI agent initially reported the endpoint response time as 47 seconds instead of the correct 47 milliseconds.
- ▪The author utilized the AI Agent Debugger to identify and fix the misunderstanding regarding the unit of measurement.
- ▪After making adjustments to the response schema and system prompt, the agent consistently returned accurate response times.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/sebbasstian/dai-ly-lien-tuc-noi-doi-toi-cho-den-khi-toi-dung-trinh-go-loi-ai-agent-apidog-1215 |
| Publication time | Wed, 20 May 2026 07:26:16 +0000 |
| Retrieval time | 2026-05-20T07:35:00.539Z |
| Last seen | 2026-05-20T07:35:00.539Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | K9rAocMrl5cH |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3818120) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sebastian Petrus Posted on May 20 • Originally published at apidog.com Đại Lý Liên Tục Nói Dối Tôi. Cho Đến Khi Tôi Dùng Trình Gỡ Lỗi AI Agent Apidog. Một buổi chiều thứ Ba, tác nhân AI của tôi khẳng định endpoint /users phản hồi trong 47 giây. Số đúng là 47 mili giây. Thử Apidog ngay hôm nay Tôi mất hai ngày để lần theo lỗi này. Tôi thêm log vào MCP server, chỉnh system prompt, đọc từng token phản hồi của mô hình. Mỗi thay đổi làm câu trả lời nghe hợp lý hơn, nhưng vẫn sai.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
