We have a platform (Gram) which is serverless MCP. Now users can launch MCP servers that only have 3 tools, search, describe, execute. Gram handles the tool routing, and execution (acting sort of like the sandbox). So the client only ever needs to know about those three tools. Everything else is abstracted.
Hi all! we wrote this post a couple weeks ago. The TL;DR is that we recently built an API Key authorization flow that can integrate into any API provider's Gateway and makes it trivially easy for them to provide their users self-service API key management: https://speakeasyapi.dev/docs/product-reference/speakeasy-pl...
To get that working we first evaluated every commonly-used auth method before deciding on a fairly unique approach, Signed Tokens as API Keys, but with 1 Signing Key Per API key.
Happy to answer any questions people have about this novel approach, or anything API auth related. If anyone wants to try out the tool here's the sign up for the waitlist: https://speakeasyapi.dev/request-access/
Depending on the nature of the API, you could wrap it in a react component (if that's likely what users would do), and then embed it onto your landing page so that people could interact with it.
I knew I was a distractible person, but I never realised the degree to which having the URL and tabs at the top of my browser was a drag on my productivity until I began using Arc. Now, I basically always keep Arc in focus mode and it has had a really positive impact on my concentration. There are definitely things about the browser that bother me, but this one benefit has been enough to make it my new default.
This is very cool, it's good to see people working to build bridges that make it easy to interface with blockchain data. Do you guys have an openAPI spec for the API?
Hi I'm actually working on a guide for this exact topic. My basic thoughts are that there's currently no magic bullet solution and it depends primarily on your technical ability and resourcing:
-0 technical skills: notion or atlassian
-pseudotechnical (github & markdown skill): gitbook, or readme
-technical with resourcing constraints: docusaurus, or hugo or mkDocs.
-technical w/o constraints: custom react site: Markdoc + Next.js or Gatsby
It works. The results are not spectacular, merely passable. We think in the near future we will build our own plugin for the community. If you ever want to char docs, get in touch!
Wha's always boggled me about Postman is that it doesn't have autosave. It's 2022, what doesn't have autosaving? So thank you for adding auto-saving, huge improvement on Postman!
We have a platform (Gram) which is serverless MCP. Now users can launch MCP servers that only have 3 tools, search, describe, execute. Gram handles the tool routing, and execution (acting sort of like the sandbox). So the client only ever needs to know about those three tools. Everything else is abstracted.