DDX for PostgreSQL — API Reference
OpenAPI 3.1 specification for the public HTTP surface, rendered with Swagger UI.
OVERVIEW
pg.ddx.io exposes three complementary HTTP APIs, all public and read-only:
- REST — the
/api/v2/*JSON surface (git repos & commits, mailing-list search, code & symbol search, code at a commit with/api/v2/code/at, community/contributor data) plus the public-inbox-compatible/m/*views and the code browser/c/<repo>/<rev>/<path>(HTML). Documented below by an OpenAPI 3.1 specification rendered as an interactive Swagger UI explorer. Raw spec at/openapi.yaml. - GraphQL — a single endpoint at
POST /api/graphql. Open/api/graphqlin a browser to get the GraphiQL explorer (schema introspection populates the docs and autocomplete automatically). - MCP — the Model Context Protocol endpoint at
/mcp(JSON-RPC over HTTP) for AI agents; see MCP tools. - UTCP — the same JSON API as a UTCP 1.1 manual at
/utcp: one HTTP tool per operation, each with the URL and method to call, generated from the OpenAPI spec. The MCP tools are not in it; any MCP client reaches them at/mcp.
Every documented endpoint is served live at https://pg.ddx.io by
the open-source pg.ddx.io server codebase.
All JSON endpoints send Access-Control-Allow-Origin: *, so they are
usable directly from a browser. The /m/* URLs render either HTML or
JSON depending on the format query parameter or the
Accept header.
The raw OpenAPI document lives at
/openapi.yaml — embed it in
your own tooling, generate clients with openapi-generator, or
point Postman/Insomnia/Bruno at it.
SPECIFICATION
RELATED
- How To Use Each Endpoint — narrative usage guide for HTTP, IMAP, NNTP, POP3, Git, MCP.
- About pg.ddx.io — what this service is and why it exists.
- openapi.yaml — raw OpenAPI 3.1 spec, served directly by the service.
- /utcp — the UTCP manual of the JSON API, for clients that call tools over HTTP themselves.
- /api/graphql — interactive GraphiQL explorer for the GraphQL API.