pouet.chapril.org est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Chapril https://www.chapril.org est un projet de l'April https://www.april.org

Administré par :

Statistiques du serveur :

1,1K
comptes actifs

#api

14 messages14 participants0 message aujourd’hui

"When thinking about a large language model input and output, a text prompt (sometimes accompanied by other modalities such as image prompts) is the input the model uses to predict a specific output. You don’t need to be a data scientist or a machine learning engineer – everyone can write a prompt. However, crafting the most effective prompt can be complicated. Many aspects of your prompt affect its efficacy: the model you use, the model’s training data, the model configurations, your word-choice, style and tone, structure, and context all matters. Therefore, prompt engineering is an iterative process. Inadequate prompts can lead to ambiguous, inaccurate responses, and can hinder the model’s ability to provide meaningful output.

When you chat with the Gemini chatbot, you basically write prompts, however this whitepaper focuses on writing prompts for the Gemini model within Vertex AI or by using the API, because by prompting the model directly you will have access to the configuration such as temperature etc.

This whitepaper discusses prompt engineering in detail. We will look into the various prompting techniques to help you getting started and share tips and best practices to become a prompting expert. We will also discuss some of the challenges you can face while crafting prompts."

kaggle.com/whitepaper-prompt-e

www.kaggle.comPrompt Engineering

🤖 Excited to showcase our #MCP on @microcksio early prototype!

We're exploring the ability to turn all your #API contracts into MCP-enabled simulations so that you can check #AI agents' ability to reuse them as tools! Check our @claudeai101 #Anthopic demo 🧙

youtu.be/nC6JXe1Dt58

youtu.be- YouTubeProfitez des vidéos et de la musique que vous aimez, mettez en ligne des contenus originaux, et partagez-les avec vos amis, vos proches et le monde entier.

DOGE-"Hackathon" soll alle US-Steuerdaten zusammenführen

Aufwändig getrennt gehaltene Daten von Steuerzahlern sollen flott in der Cloud zusammengeführt werden. Womöglich steuert Palantir eine Mega-API bei.

heise.de/news/DOGE-Hackathon-s

heise online · DOGE-"Hackathon" soll alle US-Steuerdaten zusammenführen
Plus via Daniel AJ Sokolov

🌘 使用 TypeScript 在 Gemini API 中搭配 OpenAI 後備方案
➤ 提升應用程式的穩定性:Gemini 與 OpenAI 的無縫整合
sometechblog.com/posts/try-gem
本文介紹瞭如何在 TypeScript 中使用 Gemini API,並設定 OpenAI 作為後備方案,以應對 Gemini API 的速率限制。作者分享了透過 OpenAI 的 TS/JS 函式庫和自定義輔助函式實現此功能的具體方法,特別是針對 Gemini gemini-2.5-pro-exp-03-25 模型每分鐘僅支援 20 個請求的限制。文章提供了具體的程式碼範例,包括定義模型類型、建立 `getCompletion` 和 `getJSONCompletion` 輔助函式,以及如何使用它們進行 API 調用。
+ 這個方法真的很有用!我一直擔心 Gemini 的速率限制問題,現在有了 OpenAI 作為
#開發 #API #Gemini #OpenAI #TypeScript

sometechblog.comUse the Gemini API with OpenAI fallback in Typescript - sometechblog.comIf you want to use Gemini’s public API, but at the same time have a safe fallback in case you have exhausted the rate limits, you can use the OpenAI TS/JS library and a few helper functions. In my particular case I needed a type-safe solution for a chartmaker app with a fallback since Gemini’s gemini-2.5-pro-exp-03-25 model is restricted to 20 request/min. First, you need to define which models you want to use so that they appear as autosuggest when you use the helper functions:

"API keys are foundational elements for authentication, but relying solely on them is inherently a risky proposal.

Firstly, there’s the reality that API keys are not securely designed — they were never meant to be used as the sole form of authentication, and as such, they aren’t really built for the task. These keys can often be easily stolen, leaked, or, in some cases (especially if generated incrementally), outright guessed. An API key is suitable for tracking usage but is poor for security.

There is also the additional reality that keys in their default state lack some critical functionality. There’s not a lot of verification built-in for identity management, and what does exist offers very little in the way of granular access control.

Ultimately, solely relying on API keys is a mistake common with novice developers but frighteningly common even in advanced products.

Best Practices
Instead of relying heavily on API keys as a sole mechanism, combine those keys with additional approaches such as OAuth 2.0 or mTLS. Implement rigorous expiration and rotation policies to ensure that keys which are made public are only useful for a short amount of time. Consider more advanced approaches, such as IP whitelisting or device fingerprinting, to add another layer of security atop the API key process."

nordicapis.com/9-signs-youre-d

Nordic APIs · 9 Signs You're Doing API Security Wrong | Nordic APIs |API security anti-patterns are common. From overreliance on API keys to a lack of rate limiting to no encryption, we explore the top ones.
#API#APIs#APISecurity