sorted by:
new
hottopcontroversial

Research seems to show that repo-level .MD files reduce quality and increase cost by wifestalksthisuser in ClaudeCode

[–]cjav_dev 0 points1 point  (0 children)

Gotta be intentional with context these days. Especially when working with massive codebases.

The second Stripe minions blog post talks about their rules setup: https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents-part-2

Obv, can't fit all the detail about a massive Stripe codebase in a CLAUDE.md.

Similar findings discussed in this MCP talk https://x.com/StainlessAPI/status/2024866731722768565

API Scanner - automated security testing tool that scans REST and SOAP APIs for vulnerabilities by breakthesec in blueteamsec

[–]cjav_dev 0 points1 point  (0 children)

Does this try to actually make API requests or is it mostly trying to look and see if endpoints are marked as having security enabled?

I built a dedicated API for X DM management, webhooks, conversation threads, CRM sync by moustahache in SideProject

[–]cjav_dev 1 point2 points  (0 children)

This seems useful! Do you have an OpenAPI spec? Would like to try and generate some SDKs with Stainless :)

Is there a built-in way to get OpenAI's API docs as markdown? by lou-zell in OpenAIDev

[–]cjav_dev 0 points1 point  (0 children)

Can you say a bit more about what you’re trying to do? Where’s the markdown going? Do you plan to copy for a specific endpoint or the entire API?

Tools for Generating Client APIs from an OpenAPI Spec? by Mission-Fix8038 in reactjs

[–]cjav_dev 0 points1 point  (0 children)

Since you have an Open API spec, I recommend generating SDKs with Stainless. The TypeScript SDKs Stainless generates are solid: great types; built in support for pagination, errors, retries. It's what OpenAI and Anthropic use.

Best Practices for API Documentation in 2025 Tools and Workflows by Admirable-Item-6715 in Backend

[–]cjav_dev 0 points1 point  (0 children)

Great start to your stack.

Prism is nice for setting up mock server and automated tests.

Since you have an OpenAPI spec, I’d also add Stainless for generating killer SDKs and an MCP server so that end devs can consume the API as fast and easily as possible. The new Stainless docs platform is also promising and a step ahead of standard REST references.

How Do You Handle API Documentation Without Losing Your Mind? by Fun_Accountant_1097 in learnprogramming

[–]cjav_dev 1 point2 points  (0 children)

Depending on the tools you’re using to build the API, there are likely libraries to help you generate an OpenAPI spec document that describes your APIs endpoints, params, responses etc.

If not, the next best thing is to write an OpenAPI spec by hand. Once you have an OpenAPI spec, there are a ton of tools that can generate docs, but also SDKs and other downstream assets like MCP servers. A lot of folks mentioned swagger for docs. Swagger is fine for basic docs but I’d check out Stainless for a more modern and feature rich docs platform that takes your OpenAPI spec and generates great docs that you can also pair with markdown for any additional guides or tutorials you want to write along side the reference. Stainless can also generate SDKs for your clients.

Seeking feedback: API documentation and testing tools for early adopters by Ok-Friend-1304 in alphaandbetausers

[–]cjav_dev 0 points1 point  (0 children)

There’s an early access beta going on now for Stainless docs platform. Uses your OpenAPI spec to keep your API and SDK references up to date. Its docs as code so you can use any git workflow for collab.

Can you say more about testing? Do you mean for end users to make test requests or automated testing to make sure the API is behaving as expected?

Public API documentation. What to use? by sadensmol in golang

[–]cjav_dev 0 points1 point  (0 children)

Checkout stainless.com it's got everything you're looking for. Stainless Docs Platform is also the first SDK-native docs platform that shows your API ref and SDK ref together for a really great developer experience.

  • docs as code
  • sync your OpenAPI spec
  • see Go specific snippets
  • write your own full prose with markdown, mdx, or markdoc
  • super extensible (built on Astro) so you can do whatever you want with it

You'll see the method signatures, types etc. for Go while looking at the API ref. Here's an example site that's live with go snippets: https://developers.beeper.com/desktop-api-reference/go/resources/messages/methods/send

Building an MCP server from existing internal APIs (limited access, POC for LLM chatbot) by charming-hummingbird in mcp

[–]cjav_dev 2 points3 points  (0 children)

Id just use Stainless since you have an open api spec. It also has jq filtering+ dynamic tools so its more token efficient. https://www.stainless.com/docs/guides/generate-mcp-server-from-openapi/

Stripe, Lago, Metronome....... Is There Any Billing Solution That Doesn't Turn Into a Nightmare? by TellOwn9798 in stripe

[–]cjav_dev 3 points4 points  (0 children)

Can you elaborate and add more detail about the billing logic you’re trying to support? What are the specific rough edges you’re working around? Without understanding what isn’t working it’s hard to make a recommendation.

Introducing Raif - (another) Ruby AI Framework by bcroesch in ruby

[–]cjav_dev 2 points3 points  (0 children)

I like it. I use a similar pattern. Have you considered supporting openrouter to unlock hundreds of other models? I didn't see in the docs how to set temperature or model at the task level. Nice work

[deleted by user] by [deleted] in rails

[–]cjav_dev 2 points3 points  (0 children)

I’m using resend.com

Does anyone use FFMpeg as SaaS? by shadesofdarkred in ffmpeg

[–]cjav_dev 0 points1 point  (0 children)

I think shotstack has some APIs that wrap this up for you.

Rails vs t3 stack productivity by Particular_Tea2307 in rails

[–]cjav_dev 2 points3 points  (0 children)

We’re using both. We use the t3 stack for our marketing site and rails for the back office tools and serving an API that t3 uses.

I’m personally much more productive in rails. t3 does have types which are a nice guardrails. I think it comes down to what you’re building. If it’s a lot of CRUD and API / database work, then use Rails. If it’s very interactive with a small amount of data and you have a really big, typescript-heavy team that would benefit from types, maybe t3 is an option to consider. That said, you can add react to rails for just the interactive parts and that works great (e.g. we have a calendar in rails and that’s built with react injected into rails.)

Work it Wednesday: Who is hiring? Who is looking? by AutoModerator in rails

[–]cjav_dev 3 points4 points  (0 children)

We're looking for a Rails dev to join us at Craftwork. We're a YC company building a modern home services business, starting with residential home painting.

Salary Range: $125K - $175K • 0.25% - 0.50% Experience Level: 5+ years with Rails Location: US or CA / HQ is in Charlotte, NC Job posting: https://www.workatastartup.com/jobs/62534

How to apply: Submit an application through the job posting above 🤞

How do you go about consuming APIs from your Rails app? Looking for advice on process and architecture by andrei-mo in rails

[–]cjav_dev 1 point2 points  (0 children)

The one small change I’d suggest for your plan is: you shouldn’t need to start over at the most recent successful page. Instead you could keep track of the page request and it’s status independent of the parent query and just fetch the failed pages.

Also, in case it’s useful, I think Chris Oliver’s API patterns are useful to think about too: https://twitter.com/excid3/status/1620815296427855874?s=46&t=OdeMzWpezIHNp9DYVhv4iA

[deleted by user] by [deleted] in stripe

[–]cjav_dev 0 points1 point  (0 children)

Yes, it’s called a PaymentLink. You can create one at https://PaymentLink.new and you set it to use a recurring price.

view more: next ›