10 / Start with the artifact
Paste an API artifact and turn it into a working investigation
Workbench detects cURL, OpenAPI, Postman, JSON, and URLs, then helps normalize, run, inspect, and export the result.
curlopenapi.yamlpostman.jsonURL
↓ DETECT · NORMALIZE ↓
runmocktestexport
Working reference
What goes in, what comes out, and what the result can prove.
Concrete artifact
Detection should remain reversible
Input: curl -X POST https://api.example/orders -d '{...}'
Detected: HTTP request
Available next steps: send · mock · test · document
Original input: retainedReview sequence
Three checks before the result becomes a decision.
Detection
Show the detected type and why it was selected.
Normalization
Keep a structured representation without discarding the original.
Routing
Offer only workflows that can consume the detected artifact.
Limits
What this workflow does not prove.
- Ambiguous text may require the user to select the artifact type.
- Parsing does not validate business correctness.
- Remove secrets before pasting third-party artifacts.
Questions worth answering
Before you put it into a real workflow.
What can I paste?
Common inputs include cURL, URLs, OpenAPI, Postman collections, JSON, and request-like text.
Does detection change my input?
The original input remains available while a normalized representation is created for the selected workflow.
Can I export the result?
Yes. Available exports depend on the input and workflow, and may include OpenAPI, Postman, cURL, or HTTPStatus formats.
Next move
Start with one concrete API problem.
Keep the first step small. Move into a workspace when the result deserves to be saved, repeated, or shared.