Powerful and verified APIs for developers and agents, powering the worlds most innovative applications API Catalog: https://nitter.cf/t.co/ecgs7F4lZS
Netherlands
Joined November 2020
- Tweets621
- Following253
- Followers237
- Likes670
ApyHub retweeted
When did you last open your ~/.claude or ~/.codex folder? 👀
A GitHub issue says Postman’s desktop app added plugins and a startup hook there without asking. Still open.
Auditing mine tonight.
How do you keep your agent config clean?
#ClaudeCode #DevTools
ApyHub retweeted
Most API clients open a new request as a form: URL bar, then tabs for Params, Headers, Body, Auth, Scripts, Tests. Some stay empty.
In Voiden you paste the curl from the docs into a .void file and get only the blocks it needs: Endpoint, Headers, JSON body etc.
Need auth? Add that as a new block.
try Voiden here: voiden.md/download
#DevTools #webdev
ApyHub retweeted
Voiden 2.3.3 is out 📷
→ Reworked Commit History: hover a commit for author, message and files
→ Requests inherit .env files from parent folders
→ Optional request fields
→ Choose what opens on startup
→ Fixes across Git, envs, gRPC and saving
voiden.md/download
ApyHub retweeted
Hi X 👋 I'm Sandeep, a dev working where APIs meet AI.
I'll be sharing:
→ Dev productivity tips
→ Lessons from building with AI agents
→ APIs you shouldn't build from scratch (and what to use instead)
What are you building with AI right now?
#DevelopersIndia #BuildInPublic
ApyHub retweeted
I work on apyhub.com, so SaaS teams can get lots of APIs from one place instead of a new vendor for every feature. Curious, which vendor gives you the most headaches right now? 😅
ApyHub retweeted
cloud run, firestore, vertex, X API, a scraper, a scheduler, vercel.. that's a lot of bills for one autoposter 😅 which piece breaks the most? (for the page-scraping part, @apyhub has APIs that can help)
ApyHub retweeted
Building something that needs to know about food and wine?
Happy to have @spoonacular's food insights on @ApyHub, ready as APIs: food search, ingredients and wine pairing.
We asked what goes with salmon. Pinot noir.
apyhub.com/providers/skycraf…
ApyHub retweeted
We built an MCP server for 1500+ Tools
We recently built an MCP server that lets your agent use 1500+ tools from one connector.
The idea is pretty simple:
Instead of wiring an MCP server to one API, then another, then another, the agent can search the catalog, find the API it needs, see what it does, and call it.
@ApyHub has 450+ services and 1,500+ endpoints across things like file conversion, OCR, data extraction, validation, geolocation, SEO, image processing, and AI.
So you can give an agent a fairly small set of tools and still have access to a much larger set of capabilities.
Some examples:
- convert a Word document to PDF
- extract text from a PDF
- OCR a scanned document
- extract text from a webpage
- compress a video
- -generate a QR code
- validate an EU VAT number
- validate email DNS
- convert currencies
- parse a resume
- check SERP rankings
- generate speech from text
The useful part is that these can also be chained.
For example:
Take a scanned invoice → OCR it → extract the data → validate the VAT number → convert the currency → generate a PDF.
Or:
Extract a webpage → check readability → summarize it → check its search ranking.
You don't have to build those workflows ahead of time. The agent can compose the calls based on the task.
There is also curation.
Giving an agent 1,500 tools creates tool bloat and overwhelms the model with context.
Instead, you can select which endpoints an agent may use: a document agent might have 15–20 endpoints, while an enrichment agent uses a different set.
One other thing we cared about was credentials.
Normally, connecting an agent to ten vendors requires ten API keys stored somewhere in the agent’s environment or context. Those traces eventually appear in logs, observability tools, bug reports, etc.
With ApyHub, the agent uses one scoped key.
The MCP server is at:
apyhub.com/mcp
And the catalog is here:
apyhub.com/catalog
The thing I’m most interested in is what people actually try to make their agents do with the catalog. There are a lot of boring utilities in there already, but there are always going to be things we haven't covered yet.
If you have any questions, I’m happy to assist :)
ApyHub retweeted
One small developer task that can become surprisingly annoying:
turning a webpage into a clean PDF.
You can build the conversion yourself, reach for a library, deal with rendering differences, then spend time maintaining something that isn't really your product.
I explored @apyhub Webpage to PDF API, and the approach is refreshingly simple.
Send it a URL, configure what you need, and the API returns the PDF while preserving the webpage's visual layout.
That makes it useful for things like generating downloadable reports, archiving web content, or adding PDF exports to a product without building the conversion layer from scratch.
This is the kind of API utility I like.
Not because it's flashy, but because it removes a small piece of engineering work you probably don't want to own forever.
ApyHub has 200+ certified APIs across common developer utilities, so there's plenty more to explore.
apyhub.com/catalog
ApyHub retweeted
If I had to assemble a lean open-source stack for content, research, and AI workflows tonight, I'd start here:
1. VoidenHQ/voiden
github.com/VoidenHQ/voiden
Why: API documentation and testing get messy when they are not versioned like code
2. karakeep-app/karakeep
github.com/karakeep-app/kara…
Why: saving links is easy, finding the useful thing later is the real problem
3. usebruno/bruno
github.com/usebruno/bruno
Why: API testing should not turn into a whole separate SaaS universe
Not a top-tools list. More like a compact operating system for moving without guesswork.
Which piece would you install first?
ApyHub retweeted
Good evening frens
I recently explored @VoidenMD and I really like the idea behind it.
If you build APIs, you probably know the struggle of switching between different tools for testing, documentation, notes, and requests It quickly becomes messy.
@VoidenMD brings everything together in one place.
Instead of keeping your API requests in one app, your docs in another, and your tests somewhere else, Voiden lets you manage them together using simple Markdown files Since everything is stored like code, it's easy to organize, version with Git, and share with your team.
What also stood out to me is that it's offline-first and open source You don't need to create an account or depend on a cloud service just to work on your APIs.
If you're a developer, here's how to explore Voiden:
• Visit the website and understand the main workflow
• Download the desktop app for your operating system
• Read the documentation to learn the basics
• Open the GitHub repository to see the source code and examples
• Create your first API request in Markdown
• Try organizing endpoints, headers, authentication, and parameters into reusable blocks
• Connect it with Git to track changes over time
• Experiment with scripting using JavaScript, Python, or Shell for more advanced automation.
I enjoy discovering projects that solve real developer problems instead of adding more complexity Voiden feels like one of those tools worth checking out. I saw inside @myfanforce Spotlight
ApyHub retweeted
I spent some time exploring @apyhub today, and honestly, it’s much more comprehensive than I expected.
A lot of developers end up rebuilding the same things over and over again PDF conversion, OCR, file processing, validation, image analysis… They’re essential, but they rarely define what makes a product unique.
That’s where ApyHub stands out. Instead of stitching together dozens of services, it brings hundreds of APIs under one platform with a single API key. Even better, it’s built with AI agents and MCP compatibility in mind, not just traditional applications.
What caught my attention isn’t simply the size of its API catalog. It’s the philosophy behind it: developers should spend their time building features that create value, not maintaining repetitive infrastructure.
With over 200 APIs and 1,000+ endpoints, ApyHub already offers a solid foundation. Combine that with enterprise grade security, a unified subscription model, and an AI first vision, and it becomes a platform that’s hard to ignore.
As AI continues to evolve, I believe platforms that simplify integrations instead of adding more complexity will become increasingly valuable.
ApyHub is definitely one I’ll be keeping an eye on.
👉: apyhub.com
ApyHub retweeted
Most teams don't need more AI models.
They need fewer APIs to stitch together.
That's why platforms like @apyhub are interesting:
→ File conversion
→ Data extraction
→ PDF tools
→ Utility APIs
→ AI-ready workflows
Less time building plumbing. More time shipping products.
What API do you wish existed but doesn't yet?
🤝 Paid partnership
ApyHub retweeted
10 open-source repos I’d test for marketing, content, and AI-product growth.
Not a random GitHub dump. The filter is simple: can this repo remove a real workflow pain or create a content angle people understand fast?
1. generalaction/emdash
github.com/generalaction/emd…
Why: multiple coding agents need orchestration, not eight terminal tabs and hope
2. keploy/keploy
github.com/keploy/keploy
Why: API tests are painful when mocks, traffic and real behavior live in separate worlds
3. rerun-io/rerun
github.com/rerun-io/rerun
Why: robotics and multimodal systems need visual logs people can actually understand
4. VoidenHQ/voiden
github.com/VoidenHQ/voiden
Why: API documentation and testing get messy when they are not versioned like code
5. langgenius/dify
github.com/langgenius/dify
Why: AI apps need workflows, data and evaluation, not just one more prompt window
6. Fincept-Corporation/FinceptTerminal
github.com/Fincept-Corporati…
Why: internal dashboards should be faster to ship than a full custom app
7. lightdash/lightdash
github.com/lightdash/lightda…
Why: business dashboards become slow when every metric needs a custom analyst pass
8. metabase/metabase
github.com/metabase/metabase
Why: teams need answers from data without turning every question into a data-team ticket
9. koala73/worldmonitor
github.com/koala73/worldmoni…
Why: news and global signals become hard to track when everything is scattered across random feeds
10. usebruno/bruno
github.com/usebruno/bruno
Why: API testing should not turn into a whole separate SaaS universe
Which one should I break down first?
