Product index / Choose by outcome

Choose a workflow by the problem you need to solve

A curated directory of HTTPStatus public products. Focused formatters and protocol helpers live inside the signed-in application.

Start with API mocks Open app tools

index://outcomecurated

01Unblock a dependency02Reproduce a failure03Protect a release04Operate with evidence

Choose by blocked outcome

Six useful doors. Not six hundred landing pages.

01Unblock developmentCreate a dependency before the production API exists.02Reproduce a failureKeep the request, response, and first divergence together.03Protect behaviorTurn client expectations into inspectable API tests.04Review a changeClassify contract impact before clients discover it.05Connect an assistantExpose bounded tools through a visible protocol surface.06Review API riskSeparate observed security evidence from inference.

Working reference

What goes in, what comes out, and what the result can prove.

INPUTBlocked engineering outcome

OUTPUTThe smallest workflow that produces useful evidence

Concrete artifact

Choose by the decision you need to make

Need a dependency now       → Mocks
Need to reproduce a failure → Client or Debug
Need release confidence     → Contract or API Testing
Need operational evidence   → Trace, Log or Shield

Review sequence

Three checks before the result becomes a decision.

Input fit

Can the workflow consume the artifact you already have?

Output fit

Does it produce evidence for the decision?

Persistence

Use the workspace only when the result deserves reuse.

Limits

What this workflow does not prove.

A directory should route work, not create hundreds of near-duplicate landing pages.
Some investigations require more than one workflow.
Private execution and saved history remain inside the app.

Questions worth answering

Before you put it into a real workflow.

Where did the individual utility pages go?

Focused utilities are available in the signed-in app rather than as hundreds of public landing pages.

Which product should I try first?

If another team is blocked, start with mocks. If behavior is failing, start with the HTTP client or debugger. If release safety is the issue, start with contracts or testing.

Are public pages interactive?

These pages explain the product. Execution and saved work happen in the relevant workflow, often inside the app.

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.

Start with API mocks Talk to a human