# Openapi Graph

> OpenAPI front example; a graph whose step turns an OpenAPI operation into a sealed tool result.

- Skill: `runxhq/openapi-graph` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add runxhq/openapi-graph`
- Raw SKILL.md: https://api.skillmd.com/api/skills/runxhq/openapi-graph/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: runxhq (https://skillmd.com/u/runxhq)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/runxhq/openapi-graph

---

# OpenAPI graph

A single-step graph that drives the OpenAPI external-adapter sub-skill. The
runtime routes the graph step's `external-adapter` source through the
source-adapter registry to the external-adapter executor, which spawns the
declared adapter process. The adapter resolves an OpenAPI operation
into a concrete HTTP request and the runtime seals it. Its manifest declares a
required network scope because the adapter performs the outbound fetch.

This is the concrete proof that the core runs from other specs, not just MCP.
Run `examples/openapi-graph/run.sh` to start the local fixture endpoint and fail
hard unless the graph state proves the GET executed and returned the expected
pet payload, and the receipt directory contains a signed `runx.receipt.v1`.

The inline harness case expects that fixture endpoint to be running. Use
`run.sh` for the hermetic demo entrypoint; bare `runx harness
examples/openapi-graph` is only useful after starting `server.mjs` separately.