Middleware · Agent ↔ API-Graph · JVM

Execute your API graph.
Get back a Rundown.

The middleware between an agent and your API-Graphs — an AI agent, or your own JVM code acting as one. Describe a workflow of interdependent API calls as executable API metadata; ReṼoman executes that graph on the JVM — resolving data dependencies, auth, and polling — and hands back a structured Rundown the agent reasons over.

Get started View on GitHub

v0.9.14 · Apache-2.0 · from the API-first SaaS company, Salesforce · no licensed Postman SDKs

rundown executing
  1. 01 POST /objects 142 ms
  2. 02 GET /objects 88 ms
  3. 03 GET /objects/{id} 76 ms
  4. 04 PATCH /objects/{id} 110 ms
rundown.toJson(VERBOSE) 
{ "stepReports": [ 4 — all passed ], "mutableEnv": {…}, "stats": {…} }

// how the middleware executes

A graph in. A Rundown out.

Think of the Postman Collection Runner walking a collection step by step — but inside a Java/Kotlin program, resolving the dependencies between calls. Today that metadata is serialized in the Postman V2/V3 schema; reading Postman-schema metadata no more makes this "a Postman tool" than emitting JSON makes a service "a JSON tool."

  1. 01

    Feed it the metadata

    An API-Graph: the workflow of interdependent calls, with the order and the data dependencies between them.

  2. 02

    It executes the graph

    Deterministically, on the JVM — resolving data dependencies, handling auth, polling for async outcomes, marshalling type-safe payloads.

  3. 03

    Get back a Rundown

    A structured record of everything that happened. Rundown.toJson(VERBOSITY) is the Context Information an agentic Node consumes.

Executable API Metadata the API-Graph executes ReṼoman Middleware · executes the graph resolves data dependencies, auth, polling & type-safe payloads — deterministically, on the JVM returns Rundown = Context Information for JVM code or an agentic Node

// one engine, many applications

What executing a graph unlocks

the caller port

Agentic API Orchestration

The deterministic step beneath an agentic workflow: metadata in, the Rundown as Context Information out.

Read more → proof it ships today

API Test Automation

Replace bespoke REST-Assured harnesses with the executable metadata your team already authored in Postman.

Read more → setup & data

Orchestrated Workflows

Drive multi-step test-data setup and end-to-end flows from one ordered, type-safe API-Graph.

Read more →

Ships today

  • The middleware substrate: an API-Graph in → deterministic execution on the JVM → a Rundown out
  • Resolves data dependencies, auth, and polling between steps
  • A Rundown whose toJson(VERBOSITY) is structured Context Information
  • Type safety, dynamic hooks, timing metrics, and the Postman pm.* script APIs — written ground-up for the JVM

Roadmap — direction, not shipped

  • Format-agnosticism beyond Postman V2/V3 (HTTP Client, Bruno, …)
  • MCP tool-definition autogen from OAS + API-Graph metadata
  • Dynamic coupling of agentic workflows to API-Graphs at runtime

The substrate ships today; everything under Roadmap above — including the AI-agent glue — is direction, not present-tense. ReṼoman is honest about the line.

Wire it into your JVM project.

One entry point — ReVoman.revUp(config) — executes the graph and hands you the Rundown.

Get started Why ReṼoman?