Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I am excited to announce the launch of the Postman Context Graph API! The Context Graph API lets an agent see your API ecosystem as a connected system. You do not need to replace your model, agent, or IDE. You give the tools you already use access to the...

54,955 Aufrufe • vor 10 Tagen •via X (Twitter)

6 Kommentare

Profilbild von Abhinav Asthana
Abhinav Asthanavor 10 Tagen

With the Context Graph, your agent is no longer limited to whatever code you put in front of it. In our benchmark, we asked each model to identify every service across a large public software ecosystem that exposes HTTP endpoints. The model could search the repositories in its local checkout, but that checkout represented only 129 of the 498 services the Context Graph surfaced. The other services lived in repositories outside the checkout, existed without their own repository, or were separate components buried inside larger repos. No amount of better searching could find all of them because much of the code was never available to search in the first place. You cannot grep what was never in the checkout.

Profilbild von Abhinav Asthana
Abhinav Asthanavor 10 Tagen

We tested three different models across seven scored prompts, and the Context Graph improved accuracy in 18 of the 21 model-prompt pairs. It gave each model a much better place to start, so instead of searching the entire estate from scratch, it could focus on verifying the relationships that actually mattered.

Profilbild von Abhinav Asthana
Abhinav Asthanavor 10 Tagen

You can really see the difference when you ask who calls an API before making a breaking change. On its own, Opus found 9 of the 13 real callers. With the Context Graph, it found 12. Its accuracy jumped from 0.777 to 0.943. It found more of the right callers and guessed less.

Profilbild von Abhinav Asthana
Abhinav Asthanavor 10 Tagen

The model also did less work to get there. Across the benchmark, Opus cost 27% less with the Context Graph and Astra cost 20% less. On the HTTP-endpoint question, Opus went from $37 per run to $10, used about a quarter of the input tokens, and made half as many tool calls. Once the graph pointed it in the right direction, it did not need to burn time and tokens rediscovering the ecosystem one search at a time.

Profilbild von Abhinav Asthana
Abhinav Asthanavor 10 Tagen

Checkout the Context Graph API here along with instructions to integrate your agents:

Profilbild von Benۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗ☁️
Benۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗۗ☁️vor 9 Tagen

This looks dope, heard it runs on Daytona tho. If they cause downtime lmk. We'll provide 50k credits and get you back online then.

Ähnliche Videos

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 Aufrufe • vor 4 Monaten