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

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

На главную

Most API docs only show HTTP endpoints, but developers write code with SDKs. We're doing things differently with the Stainless Docs Platform, now available in early access. Stainless Docs are SDK-native. They update automatically when your API changes. Devs see your docs in the language of their choice with...

25,732 просмотров • 8 месяцев назад •via X (Twitter)

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

I'm concerned we're entering a local maxima with CLIs, they're the wrong interface for agents The right interface is regular REST APIs with CIMD (same spec that MCP uses to allow for dynamic client registration) Your agent then writes code to interact with the API (like Cloudflare codemode) Think about how this works for humans today for the following action: "I want to set a DNS record on my domain" -> You Google "Vercel set DNS records" -> Docs page tells you what buttons to press -> You press buttons on a website, those call an API Now for agents, they search Google: -> "Set DNS record on Vercel Domain" -> they land on the same docs page, except it outlines what api endpoints are used as well -> the agent then calls those api endpoints for you, credentials are dynamically inserted where the agent can run them -> (optional) set auto approval policies / require approval of all non GET options by default You don't need separate interfaces for agents, nor do you really need separate skills for them CLIs have terrible discoverability, no input / output typing, they're harder to make profiles for for allowed / disallowed tools They work as a stop gap solution, but companies should be focusing on making good docs and APIs, not CLIs I've been prototyping this over at (open source if you want to play with what this world would look like - still early on it so appreciate feedback - open source and can run completely on your machine

Rhys

221,110 просмотров • 5 месяцев назад

HERMES AGENT NOW HAS AUTOMATION TEMPLATES. COPY-PASTE RECIPES FOR CRON JOBS AND WEBHOOKS. ANY MODEL. ANY DELIVERY PLATFORM. three trigger types: SCHEDULE → runs on a cadence (hourly, nightly, weekly) GITHUB EVENT → fires on PR opens, pushes, issues, CI results API CALL → any external service POSTs JSON to your endpoint all three deliver to Telegram, Discord, Slack, SMS, email, GitHub comments, or local files.Nous Research what templates ship right now: DEVELOPMENT: → nightly backlog triage (label + prioritize new issues) → automatic PR code review (posts review on every PR) → docs drift detection (finds code changes without doc updates) → dependency security audit (daily CVE scan, CVSS >= 7.0) DEVOPS: → deploy verification (smoke tests after every deploy) → alert triage (correlates alerts with recent changes) → uptime monitor (check endpoints every 30 min, notify only when something is down) RESEARCH: → competitive repo scout (monitor competitor PRs daily) → weekly AI news digest (headlines, papers, repos, industry) → daily arXiv scan (saves summaries to your notes) the webhook system is the part most people miss: hermes webhook subscribe github-pr-review \ --events "pull_request" \ --prompt "Review this PR for security, performance, and code quality." \ --skills "github-code-review" \ --deliver github_comment one command. every future PR gets reviewed automatically. the review posts as a comment directly on the PR. two cost-saving details from the docs: 1. use [SILENT] in prompts. "if nothing changed, respond with [SILENT]" prevents notification noise on monitoring jobs. 2. use script-only cron jobs for data collection. a Python script handles HTTP requests and file reads. the agent only sees stdout and applies reasoning. cheaper and more reliable than having the agent fetch. every template is copy-paste ready. every template works with any model. docs: full Hermes agent SOUL MD guide in the article 👇

YanXbt

37,775 просмотров • 1 месяц назад