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

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

На главную

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 👇

101,984 просмотров • 9 дней назад •via X (Twitter)

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

Фото профиля Context7
Context79 дней назад

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 coding9 дней назад

lets fucking go

Фото профиля Context7
Context79 дней назад

🧑‍🍳🧑‍🍳

Фото профиля Wren Castellan
Wren Castellan9 дней назад

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
Context79 дней назад

🫡

Фото профиля jan
jan9 дней назад

goated

Фото профиля Context7
Context79 дней назад

we appreciate you 🫡

Фото профиля HireTimSF.com
HireTimSF.com9 дней назад

This is really good. Love it.

Фото профиля Ashkan
Ashkan9 дней назад

Ok this is pretty great!

Фото профиля AI Mastery Guide
AI Mastery Guide9 дней назад

Agent readable docs is a smart move

Фото профиля Nart Madi
Nart Madi9 дней назад

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
Gregor9 дней назад

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
AWE8 дней назад

does webmcp cover docs behind auth

Фото профиля Context7
Context78 дней назад

not right now. it only covers public docs.

Фото профиля Rey
Rey9 дней назад

Or simply clone the repo

Фото профиля Modelplane
Modelplane9 дней назад

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 🥕8 дней назад

Ha. Fucking love this 👏

Фото профиля AXIALIS | Desktop App Tools
AXIALIS | Desktop App Tools8 дней назад

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

Фото профиля Tharsan
Tharsan9 дней назад

This video is amazing

Фото профиля Felipe Suaza
Felipe Suaza9 дней назад

@G_Programming mira Alan que tal?

Фото профиля Rayane
Rayane9 дней назад

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

Фото профиля SkillPod
SkillPod8 дней назад

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

Фото профиля DocsMint
DocsMint9 дней назад

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

Фото профиля Yves
Yves8 дней назад

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.

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