Introducing the Context Graph API: One Map of Your API Ecosystem

Postman’s Context Graph API is presented as a private, authenticated knowledge graph designed to give coding agents organization-wide operational context beyond a single repository, including APIs, services, schemas, deployments, runtime calls, telemetry, external systems, and ownership information. By connecting existing data sources through Postman, organizations can create a graph that refreshes nightly and can be queried asynchronously through a single `/asks` endpoint to identify likely dependencies and potential blast radius before code changes are made. In a controlled benchmark spanning 468 repositories, three models, and infrastructure-related questions, Postman reports that graph-assisted agents used fewer tokens, made fewer tool calls, reduced costs, and improved accuracy in most prompt-model comparisons, particularly for runtime dependencies that cannot reliably be found through code search alone. The company emphasizes that graph results are intended as leads that agents must still verify in source code, acknowledges that its index may not precisely match the tested code version, and argues that missing operational evidence—not necessarily model capability—is a major cause of cross-service failures. Postman says the API works with existing models and development environments, uses typed nodes and sourced relationships to reconcile code, specifications, and production signals, and will also become available through the Model Context Protocol.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.