GitHub delivery evidence
Build and verify the change with supported GitHub context.
OpenAPIValidateSecretsMCPSSRF-safe
Verify the contract, not just the code.
Import or sync OpenAPI documents, watch your API surface change over time, and run real requests with per-environment secrets, all through a proxy hardened against SSRF.
openapi.yaml · endpoints
- GET21
- POST11
- PATCH6
- DELETE4
42 endpoints18 secured3 deprecated
API Explorer lives in Engineering, beside the build.
One connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.
BD
Discovery
Feedback
Product
Engineering
Release
Reliability
Evidence
Engineering
Build and verify the change.
Available now
VCS insights
Inspect delivery workflow activity in the connected release workspace.
Test intelligence
Investigate test outcomes and flakiness evidence across runs.
API Explorer
Keep supported API contracts inspectable alongside release evidence.
Compute pricing
Compare public cloud compute pricing as planning evidence.
A workbench, not a viewer.
Bring the spec in, watch it change.
Import from a URL, an upload, or a connected GitHub repo; git specs auto-sync and every change becomes a numbered, immutable revision.
url · upload · gitvalidatedrevision history
- 01
Source
url · upload · git
- 02
Validate
parse and check the contract
- 03
Revision
rev 14 · 42 endpoints
- 04
Drift
git specs polled for changes
The same variable, resolved per environment.
Named environments scope to org, team, or a single spec, with typed string, url, and secret variables that are encrypted at rest.
org · team · spectyped variablessecrets encrypted
- BASE_URLurl
- API_TOKENsecret
- TENANTstring
Run requests through a hardened proxy.
The server-side proxy blocks internal targets, checks the resolved IP against DNS rebinding, and is permission-gated and audited.
ssrf-guardedhard timeoutaudited
- 01
Build request
method, headers, template
- 02
SSRF guard
resolve and check the target IP
- 03
Execute
manual redirects, hard timeout
- 04
Response
status, headers, duration
Let a teammate ask the API, without asking a developer.
Someone in customer success needs to know if there’s an endpoint for bulk refunds. Today that means pinging an engineer, who then digs up the docs, or worse, turns on a tool and walks them through it. The answer exists. Getting to it costs two people an afternoon.
MCP Explorer exposes your tracked specs as a Model Context Protocol server, so a teammate’s AI assistant can search the surface, read the schema, and draft the call. Share a spec with a link and they can explore it directly. Every request still runs through the same permissioned, SSRF-hardened proxy, so self-serve never means unsafe.
Old way · waits on a dev
“Which call handles refunds? Can you enable the docs for me?”
With lube · self-serve
Asks the MCP Explorer, finds the endpoint, runs it in the sandbox.
MCP Explorer
Customer success
Support
Partner engineer
AI assistant
Search the surface
Ask in plain language; the MCP server returns matching endpoints and schemas.
Share a spec link
Hand a colleague a link instead of a screenshot of the docs.
Run it safely
Calls still pass permissions and the SSRF-safe proxy, and land in the audit log.
The details that make it trustworthy.
Import sources, sync triggers, variable types, and per-revision stats are all first-class, so the contract stays honest over time.
Spec sources
Three ways in.
urluploadgit (GitHub)
Sync triggers
How a re-check fires.
createmanualscheduledwebhookupload
Variable types
With scopes.
stringurlsecretorgteamspec
Methods tracked
Counted per revision.
GETPOSTPUTPATCHDELETEHEADOPTIONS
Spec stats
Health over time.
endpoint countdeprecatedsecuredmodelstags
Proxy limits
Safety by default.
256KB bodymanual redirecthard timeoutbounded uploads
Honest scope
API Explorer is an OpenAPI and REST workbench. Git-sourced specs are GitHub-only, there is no GraphQL or gRPC model, and execute is a single request and response, so there are no multi-step runners or pre-request scripting.
See what the contract implements.
Keep your API contracts inspectable and runnable.
Start free
Bring supported OpenAPI documents into the loop.