Postman explains how Bedrock powers its production-scale Agent Mode for developers
Postman explains how Bedrock powers its production-scale Agent Mode for developers
AI Agents & Automation

Postman explains how Bedrock powers its production-scale Agent Mode for developers

AWS Machine LearningOct 9, 2026

Postman says Agent Mode uses Amazon Bedrock and task-specific tools, context handling and inference controls to support its developer community at production scale.

Postman has outlined how it built Agent Mode, an AI interface for working across API testing, documentation, discovery and implementation. The company says its product serves a community of 40 million developers; the system runs on Amazon Bedrock, which provides managed access to foundation models without Postman operating its own model-serving infrastructure.

A central design challenge was keeping the agent’s available actions focused. In Postman’s testing, tool-selection errors increased when more than approximately 40 tools were visible to the model. Its architecture can search a catalog of more than 170 tools and narrow the selection to approximately 15 relevant tools for a task. The agent also uses schema-aware reads to query structured data, reducing the need to create a separate tool for every question.

Postman says missing or poorly prepared context caused more failures than missing capabilities. It built dedicated handlers to extract useful details about selected product objects rather than passing along data shaped primarily for the application interface. Agent Mode also combines its tools and instructions with a retrieval-augmented knowledge base that selects relevant product documentation for a request.

The Bedrock setup supports routing work to different Anthropic Claude models, cross-Region inference profiles and prompt caching. Postman describes using five-minute and one-hour cache checkpoints for context that changes at different rates. It has also configured zero data retention for supported models; availability depends on the model. Amazon Bedrock Guardrails can redact personally identifiable information before it reaches the model, and enterprise administrators can enable that setting.

Agent Mode requires user approval for actions that change application state. Postman says it can send requests in the background without an open tab, but approval is still required. The production implementation is proprietary and is not available as a public sample repository.

Industry Impact

A practical architecture for developer agents

Developer software and enterprise SaaS

Overview

Postman’s account shows how a developer platform can structure an agent for production use without running its own model-serving infrastructure. Focused tool selection, tailored context, documentation retrieval, model routing and caching address practical reliability and operating concerns. For product managers and engineering leaders, the approach offers design patterns for integrating agents into complex software workflows. Developers and ML engineers can assess how tool scope and context preparation affect agent behavior, while enterprise teams should note that privacy controls and user approval remain important parts of deployment.

Key Impact Points

Postman narrows a catalog of more than 170 tools to about 15 relevant tools, addressing tool-selection errors observed when more than approximately 40 are exposed.

Dedicated context handlers and documentation retrieval target a stated source of failures: missing or poorly prepared context.

Managed model access, caching, supported-model zero data retention, PII redaction options and approval for state-changing actions illustrate production operating controls.

Opportunities

Domain-specific agents for developer workflows

Developer platforms and enterprise software

Postman’s architecture points to an opportunity for developer-platform providers to build agents around bounded tasks such as API testing, documentation and discovery. Rather than exposing every action at once, a system can retrieve relevant tools and product context for each request, then use model routing and caching to manage inference. Providers could pair these workflows with administrative privacy settings and approval gates for changes to application state. The article does not quantify demand, costs or commercial results, so revenue potential remains uncertain; the design may support differentiated enterprise offerings, but would need validation with users and operational testing.

  • Controlled agents for API development workflows

    Problem: Developer agents may fail when they receive too many tools or incomplete, application-shaped context.

    Solution: Build task-specific agents that retrieve a smaller set of relevant tools, prepare product context, and draw on documentation for each request.

    Target Users: Developer-platform providers and teams building API testing, documentation, discovery or implementation workflows.

    Business Value: A focused architecture may make agent behavior more dependable and provide administrators with privacy settings and approval controls.

    Revenue Potential: Not quantified in the article; it could support enterprise product differentiation, subject to customer validation.

Reference link

https://aws.amazon.com/blogs/machine-learning/how-postman-runs-agent-mode-for-40-million-developers-on-amazon-bedrock

Image Source Link

https://blog.postman.com/wp-content/uploads/2026/06/AWS-AI-Competency-Announcement-1.jpg

Community Discussion (0)

No discussions yet. Be the first to start the conversation!