New tools for building agents
41–50 of 165 posts
Re: New tools for building agents
#42As an engineer, I have to manage the cost/service ratio manually, making sure I charge enough to handle my traffic, while enforcing/managing/policing the usage.
Additionally, there are customers who already pay for OpenAI, so the value add for them is less, since they are paying twice for the underlying capabilities.
If OpenAPI had a billing API/platform ala AppStore/PlayStore, I have multiple price points matched to OpenAI usage limits (and maybe configurable profit margins).
For customers that don't have an existing relationship with me, OpenAI could support a Netflix/YouTube-style profit-sharing system, where OpenAI customers can try out and use products integrated with the billing platform/API, and my products would receive payment in accordance with customer usage...
Re: New tools for building agents
#43swyx here. we got some preview and time with the API/DX team to ask FAQs about all the new APIs. https://latent.space/p/openai-agents-platform main fun part - since responses are stored for free by default now, how can we abuse the Responses API as a database :) other fun qtns that a HN crew might enjoy: - hparams for websearch - depth/breadth of search for making your own DIY Deep Research - now that OAI is offering…
Re: New tools for building agents
#44We handle over 1M requests per month using the Assistant API on https://rispose.com which apparently will get depreciated mid 2026. Should we move to the new API?
Re: New tools for building agents
#45I wonder why they phased out Pydantic in structured output for the Responses API.
Re: New tools for building agents
#46swyx here. we got some preview and time with the API/DX team to ask FAQs about all the new APIs. https://latent.space/p/openai-agents-platform main fun part - since responses are stored for free by default now, how can we abuse the Responses API as a database :) other fun qtns that a HN crew might enjoy: - hparams for websearch - depth/breadth of search for making your own DIY Deep Research - now that OAI is offering…
What is a "qtns"?
Re: New tools for building agents
#47swyx here. we got some preview and time with the API/DX team to ask FAQs about all the new APIs. https://latent.space/p/openai-agents-platform main fun part - since responses are stored for free by default now, how can we abuse the Responses API as a database :) other fun qtns that a HN crew might enjoy: - hparams for websearch - depth/breadth of search for making your own DIY Deep Research - now that OAI is offering…
What is a "qtns"?
Re: New tools for building agents
#48swyx here. we got some preview and time with the API/DX team to ask FAQs about all the new APIs. https://latent.space/p/openai-agents-platform main fun part - since responses are stored for free by default now, how can we abuse the Responses API as a database :) other fun qtns that a HN crew might enjoy: - hparams for websearch - depth/breadth of search for making your own DIY Deep Research - now that OAI is offering…
for anyone that likes the Agents SDK, but doesn't want their framework attached to OpenAI, we're really liking PydanticAI[0]. 0 - https://ai.pydantic.dev/
> Notably, our SDK is compatible with any model providers that support the OpenAI Chat Completions API format.
so you can use with everything, not only OpenAI?
Re: New tools for building agents
#49Is it just me, or is what OpenAI is really lacking is a billing API/platform? As an engineer, I have to manage the cost/service ratio manually, making sure I charge enough to handle my traffic, while enforcing/managing/policing the usage. Additionally, there are customers who already pay for OpenAI, so the value add for them is less, since they are paying twice for the underlying capabilities. If OpenAPI had a billin…
Two, yes, many people will pay $20/mo for ChatGPT and then also pay for a product that under the hood uses OpenAI API. If you're worried about your product's value not being differentiated from ChatGPT, I'd say you have a product problem moreso than OpenAI has a billing model problem.