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

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

На главную

Someone built a tool where you paste an OpenAPI spec and get a fully stateful sandbox that actually behaves like production No local setup No real API costs It's called FetchSandbox The workflow does this : → explores Stripe APIs → runs workflows → triggers webhooks → verifies integrations...

35,823 просмотров • 2 месяцев назад •via X (Twitter)

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

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

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

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

Claude Code + Shopify AI is f*cking cracked 🤯 Shopify just dropped an official AI Toolkit that connects Claude Code directly to your store. One prompt → Claude reads your products, rewrites your descriptions for AI shopping, and pushes the updates live. All from the terminal. All inside Claude Code. Perfect for DTC brands on Shopify who are still manually editing product pages, writing descriptions in Google Docs, and copy-pasting into the Shopify admin one product at a time. Claude Code + the Shopify AI Toolkit fixes the entire workflow: → Install the official Shopify plugin in Claude Code → Authenticate to your store → Claude reads your entire product catalog → Rewrites every description to be optimized for AI shopping → Pushes the updates directly to your store automatically → Validates every API call against Shopify's official docs before executing No Shopify admin tab-switching. No copy-pasting from a Google Doc. No hiring a copywriter to rewrite 50 product pages. What you get: → Claude Code connected directly to your live Shopify store → Product descriptions optimized for how ChatGPT, Gemini, and Perplexity recommend products → Bulk updates across your entire catalog from a single prompt → Full access to Shopify's GraphQL API — products, themes, inventory, orders, everything Claude can read and write → An official plugin built by Shopify that auto-updates as new features ship I put together a full playbook with the plugin install, the store authentication walkthrough, 5 DTC workflows to run on day one, and the exact prompts I used. Want it for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

113,609 просмотров • 4 месяцев назад

APIs are a bottleneck, not a solution! AI agents can't access 95% of the web because most websites simply don't have APIs. Supplier portals, appointment systems, regional job boards, etc., none of them have developer APIs. The valuable data lives behind logins, multi-step forms, and interfaces built for humans, not machines. That's why, for 25 years, users have been stuck with: - Search engines that index 5% of the web (nothing behind authentication) - Manual data entry or fragile scrapers that break with every CSS update That's the problem TinyFish's Mino solves. It is a web automation API that can simultaneously navigate 100s of websites and turn them into structured data. You send it URLs and a goal in plain English. It returns JSON. The approach is different from typical AI agents: Most browser agents use vision models, which screenshot the page, reason about it, decide what to click, screenshot again, and repeat. Every action needs a model call. It's slow and expensive. Mino uses AI to learn the website structure once, then executes it through deterministic code. First run figures out the site. Every run after that is code-level precision in milliseconds. It provides three core capabilities: → Navigate - Handles logins, forms, and multi-step workflows → Extract - Pulls structured JSON from any site layout → Execute - Runs 100+ sites in parallel with stealth mode The performance is production-grade: - 85-95% success rate on complex workflows - 10-30 seconds per task - Pennies per run Moreover, it works on authenticated sites, bypasses anti-bot protections, and returns clean JSON every time. Lastly, you can also integrate its MCP server with clients like Claude Desktop. I have recorded a walkthrough in the video below. Try now, link in the next tweet.

Akshay 🚀

62,659 просмотров • 7 месяцев назад

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,133 просмотров • 5 месяцев назад