
#genAI keynote speeches, workshops. coding and consulting
Helsinki, Finland
Joined August 2022
- Tweets4.9K
- Following8
- Followers63
- Likes4.2K
Bonairo retweeted
Today we're introducing the Perplexity Monitor API.
Monitor API tracks new developments on a topic or changes to specific pages on a schedule, then sends relevant updates to your application through webhooks.
Available now at $1/1k runs or URLs fetched.
pplx.ai/monitor-api
Bonairo retweeted
Kitesurf, our experimental browser engine for AI agents, is now open source. Inspect the code, run it locally, or deploy your own instance on Cloudflare Workers. cfl.re/4eHmAK6
Bonairo retweeted
Self-hosted Claude Managed Agents is now in private beta.
You can host the agent harness, sandboxes, and session history, in your own cloud or on-premises, and choose where requests to Claude are sent.
Bonairo retweeted
Introducing Gemini Decision 1, our new frontier decision model in the Gemini API.
It is $0.10 per 1M input tokens with no additional cost. With support for image, audio, video, and PDF natively, 256K context window, & 1K questions.
You can try it for free in the API!
Now in beta: Businesses in ChatGPT.
Claim your business, manage your information, and get insights on how people engage with you.
Eligible businesses can also build a Business Agent to answer customers’ questions and help them explore what you offer.
openai.com/index/introducing…
Bonairo retweeted
We're excited to unveil VINCO, our frontier AI model trained to play and win 1v1 Catan.
We've secretly deployed it on the Colonist.io global leaderboard, where it has reached both the #1 and #2 positions, consistently beating every human world champion.
Bonairo retweeted
Just promoted our new GPT-Live outbound telephony API to GA, allowing developers to make phone calls from their Live voice agent, via any SIP trunk provider (e.g, Telnyx or Twilio). Calls can use HD Voice and can send and receive keypad events (DTMF).
developers.openai.com/api/do…
Bonairo retweeted
pplx-decider-v1.2 with web grounding scores 86% on the 100 public PWS-Decisions questions, up from 51% without it.
Median latency in the test was 370 ms, with p95 at 685 ms.
pplx.ai/web-grounded-blog
Bonairo retweeted
Kubernetes is beautiful.
Every Concept Has a Story, you just don't know it yet.
In k8s, you run your app as a pod. It runs your container. Then it crashes, and nobody restarts it. It is just gone.
So you use a Deployment. One pod dies and another comes back. You want 3 running, it keeps 3 running.
Every pod gets a new IP when it restarts. Another service needs to talk to your app but the IPs keep changing. You cannot hardcode them at scale.
So you use a Service. One stable IP that always finds your pods using labels, not IPs. Pods die and come back. The Service does not care.
But now you have 10 services and 10 load balancers. Your cloud bill does not care that 6 of them handle almost no traffic.
So you use Ingress. One load balancer, all services behind it, smart routing. But Ingress is just rules and nobody executes them.
So you add an Ingress Controller. Nginx, Traefik, AWS Load Balancer Controller. Now the rules actually work.
Your app needs config so you hardcode it inside the container. Wrong database in staging. Wrong API key in production. You rebuild the image every time config changes.
So you use a ConfigMap. Config lives outside the container and gets injected at runtime. Same image runs in dev, staging and production with different configs.
But your database password is now sitting in a ConfigMap unencrypted. Anyone with basic kubectl access can read it. That is not a mistake. That is a security incident.
So you use a Secret. Sensitive data stored separately with its own access controls. Your image never sees it.
Some days 100 users, some days 10,000. You manually scale to 8 pods during the spike and watch them sit idle all night. You cannot babysit your cluster forever.
So you use HPA. CPU crosses 70 percent and pods are added automatically. Traffic drops and they scale back down. You are not woken up at 2am anymore.
But now your nodes are full and new pods sit in Pending state. HPA did its job. Your cluster had nowhere to put the pods.
So you use Karpenter. Pods stuck in Pending and a new node appears automatically. Load drops and the node is removed. You only pay for what you actually use.
One pod starts consuming 4GB of memory and nobody told Kubernetes it was not supposed to. It starves every other pod on that node and a cascade begins. One rogue pod with no limits takes down everything around it.
So you use Resource Requests and Limits. Requests tell Kubernetes the minimum your pod needs to be scheduled. Limits make sure no pod can steal from everything around it. Your cluster runs predictably.
Bonairo retweeted
i've reproduced the results from the MIT blog post today on weight-space programming. but one additional result i have to add: this is a new, step-change emerging capability that's appeared in just the latest set of models.
Bonairo retweeted
human-in-the-loop
└ human-on-the-loop
└ human-near-the-loop
└ human-cc'd-on-the-loop
└ human-legally-liable-for-the-loop
Bonairo retweeted
Describe a voice in a prompt and generate it via API. No recordings, no voice actors. Save it to your library and call it from your app.

























