Topic

API Development

All digests tagged API Development

The Search Engine for the Agentic Web — Will Bryk, Exa thumbnail

· 17:49

The Search Engine for the Agentic Web — Will Bryk, Exa

The talk introduces Exa, a search engine designed specifically for AI agents, arguing that traditional search engines (like Google) are fundamentally flawed because they are built for human recommendation rather than precise information retrieval. The core premise is that as AI systems become ubiquitous, the volume of searches issued by machines will surpass human searches by a thousandfold by 2026. Exa addresses this by providing a high-quality, customizable search API that enables agents to perform complex, database-like queries over the world's information, moving beyond simple keyword matching.

Key takeaways

  1. AI Search Volume Prediction

    The speaker predicts that in 2026, the number of searches issued by AI systems will exceed those issued by humans. This volume is expected to increase by a thousandfold in the following years, necessitating a specialized search infrastructure.

  2. The Flaw of Recommendation Engines 5:10

    Mainstream search engines are designed as recommendation engines, meaning they prioritize suggesting related content (e.g., 'shirts with stripes' when 'shirts without stripes' is queried) rather than providing exact, database-level answers. AI agents require the opposite: perfect retrieval.

  3. The Perfect Search Thought Experiment 10:05

    The ideal search involves running a Language Model (LLM) over a complex query and a document pair to determine a match. While this is highly accurate, scaling it to a trillion documents costs millions per query, making cost-optimization the primary engineering challenge.

  4. The Business Catalyst 13:45

    The company's business model was catalyzed when external users requested programmatic API access to their search engine, proving the need for an AI-focused search API, rather than just a consumer product.

Watch on YouTube Full article

SOTA Generative Media Panel — Dumitru Erhan, Shane Gu & Nicole Brichtova, Google DeepMind thumbnail

· 56:59

SOTA Generative Media Panel — Dumitru Erhan, Shane Gu & Nicole Brichtova, Google DeepMind

The session provided an overview of SOTA generative media models, highlighting new APIs like NanoBanana 2 Lite and Gemini Omni Flash. Key architectural discussions centered on the limitations of language as a sole intermediate representation for complex sensory data (taste, smell, skin tone). The consensus points toward a future requiring unified 'World Models' that integrate visual, temporal, and symbolic reasoning, moving beyond single-modality generation. Evaluation remains highly dependent on human judgment, making robust testing and field feedback critical.

Key takeaways

  1. New APIs Launched for Developers 0:15

    Google launched NanoBanana 2 Lite (the fastest/cheapest image model in the family) and the Gemini Omni Flash APIs. The Omni Flash API enables video generation and editing, priced similarly to V3 fast, making it accessible for developers [0:15-0:40].

  2. Generative Media Capabilities 2:00

    Models can now take diverse inputs (e.g., a storyboard of images, an audio track) to generate video. Furthermore, natural language processing allows for advanced video editing tasks like adding or removing elements from existing footage [1:20-3:00].

  3. The Limitation of Language as Representation 1:50

    Speakers argued that language is an insufficient intermediate representation for highly sensitive sensory data (e.g., taste, smell, skin tone). This suggests a need for more foundational representations, potentially including code or direct binary/latent space conditioning [1:50-2:30].

  4. Evaluation Challenges and Reward Hacking 0:35

    While human preference often favors AI output (e.g., sharper, more saturated images), this metric is unreliable for optimization. External testers have found 'reward hacking' artifacts, such as the model consistently adding wedding rings to hands [0:35-0:45].

Watch on YouTube Full article

MCP Release Overview: Stateless and the Big Changes in the New Spec thumbnail

· 17:48

MCP Release Overview: Stateless and the Big Changes in the New Spec

The latest MCP specification introduces a major architectural shift toward statelessness, fundamentally changing how clients and servers interact. This transition addresses scalability issues inherent in previous stateful designs by ensuring every client request contains all necessary information for the server instance to process it independently. Key updates include Multi Roundtrip Requests (MRTR) for complex flows, formalizing extensions (like MCP Apps and Tasks), and enhancing authorization adherence.

Key takeaways

  1. Transition to Stateless Architecture 3:50

    MCP is moving from a stateful model that relied on session IDs and retained server-side state (requiring an `initialize` call) to a fully stateless design. This eliminates the need for complex shared session stores or sticky load balancing, enabling easier horizontal scaling across multiple server instances.

  2. Multi Roundtrip Requests (MRTR) 7:30

    MRTR simplifies complex tool calls by breaking them into multiple, discrete requests rather than relying on open streams and waiting for responses. This significantly reduces architectural overhead when deploying services behind load balancers.

  3. Formalized Extensions 9:40

    The protocol now supports formal extensions, allowing developers to add specialized functionality without modifying the core spec. Key examples include MCP Apps (for delivering rendered UI) and Tasks (for modeling long-running processes like database migrations or human-in-the-loop workflows).

  4. Authorization Improvements 12:40

    The specification enhances adherence to OAuth standards, requiring authorization servers to return the `iss` parameter. Clients must validate this before redeeming a code.

Watch on YouTube Full article

Build Hour: Valuemaxxing with GPT-5.6 thumbnail

· 54:33

Build Hour: Valuemaxxing with GPT-5.6

The session provides a deep dive into 'Value Maxxing' with GPT-5.6, shifting focus from merely maximizing token usage to optimizing AI agents for concrete business outcomes and cost efficiency. Key strategies include selecting the optimal model (Sol, Terra, Luna) based on workload needs, implementing advanced API features like programmatic tool calling and prompt caching, and structuring agent workflows to minimize redundant context processing.

Key takeaways

  1. Shift from Token Maxxing to Value Maxxing 2:30

    Progress should be measured by the value generated (e.g., time saved, quality improved), not just the number of tokens consumed. This requires defining clear outcomes and measurable 'good' for AI agents (evals).

  2. Model Selection Strategy 4:09

    The GPT-3.5 family includes Sol (flagship/complex tasks), Terra (balanced intelligence/cost/latency), and Luna (high-volume, cost/latency sensitive) to optimize for specific workloads.

  3. Optimizing Agent Workflows with Codex 5:28

    For day-to-day coding, starting with `GPT-5.6 Soul` on medium reasoning is often sufficient. Developers can also trade tokens for time using Fast mode or utilize Chronicle to build task memory.

  4. Advanced API Techniques (Harness Optimization) 6:51

    Implement programmatic tool calling (using a JavaScript sandbox) and prompt caching to significantly reduce input token costs and processing time. Persistent reasoning and compaction also boost performance and cache efficiency.

Watch on YouTube Full article

Get started with the Interactions API thumbnail

· 8:51

Get started with the Interactions API

The Interactions API is now generally available and serves as a unified interface for interacting with various Gemini models and agents. It simplifies complex interactions—ranging from synchronous model calls to multi-step agent workflows in remote environments—by providing a single API endpoint. The API supports stateful operations by allowing users to pass the previous interaction ID, enabling iterative refinement of outputs (e.g., image editing) without re-uploading source data.

Key takeaways

  1. Unified Model Access 0:10

    The Interactions API provides easy access to all Gemini models and agents through a single interface, simplifying development across various Google AI capabilities.

  2. Stateful Interactions 4:05

    The API is stateful; developers can pass the previous interaction ID to build upon prior results, which is crucial for iterative processes like image editing or complex data processing.

  3. Advanced Capabilities 0:18

    New features include managed agents, background execution tool improvements, Deep Research, and media generation (e.g., Nano banana for images, Lyriq 3 for music, TTS for speech).

Watch on YouTube Full article

Universal 3.5 Pro Demo: Smarter Speech-to-Text with Contextual Awareness thumbnail

· 10:07

Universal 3.5 Pro Demo: Smarter Speech-to-Text with Contextual Awareness

This demo introduces Universal 3.5 Pro, an advanced Speech-to-Text (STT) model designed to significantly boost transcription accuracy through enhanced contextual awareness. Key features include passing domain-specific prompts (e.g., 'cardiology consultation'), applying context to key terms to prevent misapplication, and supporting dynamic mid-call prompt updates via API calls. Furthermore, the model retains conversation history (agent context), allowing it to accurately transcribe user input even in poor audio conditions by understanding the situational flow of a voice agent interaction.

Key takeaways

  1. Contextual Prompting for Domain Accuracy

    Passing detailed information about the audio content (e.g., 'cardiology consultation between Dr. Smith and elderly patient regarding chest pain...') dramatically improves model accuracy within specific domains. The more specific the prompt, the better the results.

  2. Contextual Key Terms 2:00

    Unlike previous methods where key terms were applied blindly, Universal 3.5 Pro allows users to define what a key term represents (e.g., 'The user's name is Zachary Klebanoff'). This prevents the model from incorrectly applying terminology based solely on acoustic similarity.

  3. Dynamic Mid-Call Prompt Updates 2:55

    The prompt can be updated in real time via the API (not available in the playground demo). This is crucial for voice agents, allowing tool calls or external data to adjust the model's context mid-conversation.

  4. Conversation/Agent Context 3:30

    The model retains previous transcriptions and accepts LLM-generated responses from a voice agent as context. This provides situational awareness, improving accuracy even in poor audio conditions and reducing the Word Error Rate (WER) on voice agent datasets.

Watch on YouTube Full article