Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Docs7 - the best way to serve documentation to agents. ◆ Automatically serve clean, agent-readable docs ◆ Native WebMCP and skills support ◆ Deep insights into AI traffic & searches We make agents love your product 👇

401,347 просмотров • 1 месяц назад •via X (Twitter)

Комментарии: 24

Фото профиля Context7
Context71 месяц назад

Your docs go live on Docs7 and reach 100,000+ active developers using Context7. Auto-prevent hallucinations with smart suggestions on 404 pages, get granular control over the content agents see, and much more.

Фото профиля Josh tried coding
Josh tried coding1 месяц назад

lets fucking go

Фото профиля Context7
Context71 месяц назад

🧑‍🍳🧑‍🍳

Фото профиля Wren Castellan
Wren Castellan1 месяц назад

okay, making docs specifically for ai agents is pretty smart 👀 cleaner docs + WebMCP + skills support sounds like a much better setup for products that actually want agents using them curious how the traffic insights lok in practice.

Фото профиля Context7
Context71 месяц назад

🫡

Фото профиля jan
jan1 месяц назад

goated

Фото профиля Context7
Context71 месяц назад

we appreciate you 🫡

Фото профиля HireTimSF.com
HireTimSF.com1 месяц назад

This is really good. Love it.

Фото профиля Ashkan
Ashkan1 месяц назад

Ok this is pretty great!

Фото профиля AI Mastery Guide
AI Mastery Guide1 месяц назад

Agent readable docs is a smart move

Фото профиля Nart Madi
Nart Madi1 месяц назад

Hey, if you want to test Docs7’s WebMCP implementation, let me know. I built the first evaluation platform for WebMCP that runs thousands of test cases across many LLMs.

Фото профиля Gregor
Gregor1 месяц назад

The traffic insights angle is what I'd have killed for. Agent hallucinating Supabase calls, no way to tell if it hit a stale page or just searched wrong. Two completely different fixes.

Фото профиля AWE
AWE1 месяц назад

does webmcp cover docs behind auth

Фото профиля Context7
Context71 месяц назад

not right now. it only covers public docs.

Фото профиля Rey
Rey1 месяц назад

Or simply clone the repo

Фото профиля Modelplane
Modelplane1 месяц назад

Clean, agent-readable docs are such a pain point. How do you handle versioning and keeping the docs in sync with code changes?

Фото профиля Jamie Barton 🥕
Jamie Barton 🥕1 месяц назад

Ha. Fucking love this 👏

Фото профиля AXIALIS | Desktop App Tools
AXIALIS | Desktop App Tools1 месяц назад

If WebMCP and a skill expose overlapping guidance, how does an agent know which source should win when they disagree?

Фото профиля Tharsan
Tharsan1 месяц назад

This video is amazing

Фото профиля Felipe Suaza
Felipe Suaza1 месяц назад

@G_Programming mira Alan que tal?

Фото профиля Rayane
Rayane1 месяц назад

@grok la diff entre ça et le mcp context7 qu’on connait tous ?

Фото профиля SkillPod
SkillPod1 месяц назад

Do agents follow the 404 suggestions, or keep retrying the URL they invented?

Фото профиля DocsMint
DocsMint1 месяц назад

Great work. Collaboration on documents between people and the agent is very important.

Фото профиля Yves
Yves1 месяц назад

if an agent pulls docs mid-task, does that payload re-enter context on every turn after? that's what actually cost me — not the fetch. the retrieval was rounding-error cheap, the re-entry was the bill.

Похожие видео