POST /auth/login
Bearer token forwarded automatically from the login step
Build readable test flows, reuse tokens and variables across requests, inspect historical results, and help your team understand why an API test failed.
Open-source core, collaborative workspaces, and enterprise-grade diagnostics.
Context-aware test flow
POST /auth/login
Bearer token forwarded automatically from the login step
GET /me
Session cookie injected into downstream requests
POST /billing/preview
tenantId variable captured from the previous response
x-trace-context propagated through the entire flow
Treat every request as one step in the same engineered workflow.
AI diagnosis
The login step returned a new session_id, but step three still references a cached header from the old session. Remap the session variable after step two.
Built for modern API teams
Core capabilities
kest is not just a request sender. It unifies execution chains, reusable context, historical results, and team signals into one engineered testing system.
See the full request chain, step health, and dependency relationships in one visual flow.
Carry tokens, cookies, headers, and variables forward without manual copy-paste.
Review execution history, timing, state changes, and regression trends over time.
Share flows, annotations, status signals, and workspaces across the whole team.
Keep test definitions readable like docs while remaining structured enough for AI.
Explain failures with request context, response data, and the surrounding execution chain.
Visualize the chain
Stop reasoning about one request at a time. Inspect the full test chain, request dependencies, variable propagation, and execution status step by step.
Flow canvas
Login
Create auth.token and session.current
Identity
Read profile.id and assemble tenant context
Billing
Inject invoice_session from shared variables
Regression report
Publish failure summary and change impact
History and collaboration
Let the team inspect historical runs, failure records, release impact, and live collaboration state in one place so regressions are easier to triage together.
Team timeline
Today 09:42 · Billing regression failed
Lina added a comment: session refresh timing looks inconsistent
Marco confirmed the change came from auth-service@v2.18
Impacted flows: checkout-flow, billing-preview
AI + .flow.md
.flow.md files keep test definitions readable like living documentation while exposing enough structure for AI to interpret context, explain failures, and speed up onboarding.
.flow.md snapshot
flow "billing-preview" uses auth.login -> user.profile -> billing.preview
capture response.token as session.current.token
Plans and pricing
Match the Miro-style four-tier structure with API testing plans for individuals, growing teams, production workspaces, and enterprise governance.
For individual developers building readable API workflows.
$0
per user / month
For small teams moving repeated tests into shared workspaces.
$8
per user / month
For teams that need reliable diagnostics and release confidence.
$16
per user / month
For organizations with security, governance, and audit needs.
Custom
annual contract
| Free | Starter | Business | Enterprise | |
|---|---|---|---|---|
| Visual test flows | ||||
| Flow canvas | Basic | Standard | Advanced | Custom |
| Request dependencies | Limited | Included | Priority | Custom |
| Step health signals | Basic | Standard | Advanced | Custom |
| Variable capture | Limited | Included | Included | Custom |
| Shared flow templates | Limited | Standard | Advanced | Custom |
| Branch comparison | Basic | Team | Advanced | Custom |
| Reusable environments | Basic | Standard | Advanced | Custom |
| Collection nesting | Basic | Standard | Advanced | Custom |
| Flow comments | Limited | Team | Included | Custom |
| Run queue | Basic | Standard | Priority | Custom |
| Scheduled checks | Limited | Standard | Advanced | Custom |
| Reusable assertions | Basic | Standard | Advanced | Custom |
| Team libraries | Limited | Team | Advanced | Custom |
| Flow import | Basic | Standard | Included | Custom |
| Flow export | Basic | Standard | Included | Custom |
| Visual diff | Limited | Limited | Advanced | Custom |
| Workspace graph | Basic | Standard | Advanced | Custom |
| Context replay | Limited | Standard | Priority | Custom |
| Shared scratchpads | Basic | Team | Included | Custom |
| Flow approvals | Limited | Limited | Advanced | Custom |
| Execution history | ||||
| Run history retention | 7 days | 30 days | Unlimited | Unlimited |
| Failure timeline | Basic | Standard | Advanced | Custom |
| Response snapshots | Limited | Standard | Included | Custom |
| Latency trends | Basic | Standard | Advanced | Custom |
| Change markers | Limited | Team | Advanced | Custom |
| Environment timeline | Basic | Standard | Included | Custom |
| Request replay | Basic | Standard | Priority | Custom |
| Regression baselines | Limited | Standard | Advanced | Custom |
| Artifact retention | Limited | 30 days | Unlimited | Custom |
| Team activity feed | Basic | Team | Included | Custom |
| Run annotations | Limited | Team | Included | Custom |
| Exportable reports | Basic | Standard | Advanced | Custom |
| Webhook events | Limited | Standard | Advanced | Custom |
| Incident links | Limited | Team | Included | Custom |
| Historical search | Basic | Standard | Advanced | Custom |
| Status archive | 7 days | 30 days | Unlimited | Unlimited |
| Run ownership | Basic | Team | Included | Custom |
| Saved filters | Limited | Standard | Included | Custom |
| Timeline sharing | Limited | Team | Included | Custom |
| Audit timeline | Limited | Limited | Advanced | Custom |
| AI diagnosis | ||||
| AI failure summary | Limited | Included | Priority | Custom |
| Root-cause hints | Limited | Standard | Priority | Custom |
| Context-aware prompts | Basic | Standard | Advanced | Custom |
| Last-green comparison | Limited | Standard | Priority | Custom |
| Suggested remaps | Limited | Standard | Advanced | Custom |
| Schema explanation | Basic | Standard | Advanced | Custom |
| Run summarization | Basic | Standard | Priority | Custom |
| Workflow generation | Limited | Standard | Advanced | Custom |
| Prompt controls | Limited | Team | Advanced | Custom |
| Sensitive-field masking | Basic | Team | Advanced | Custom |
| Custom diagnosis rules | Limited | Limited | Advanced | Custom |
| AI handoff notes | Basic | Standard | Included | Custom |
| Spec drafting | Limited | Standard | Advanced | Custom |
| Error clustering | Limited | Standard | Priority | Custom |
| Team prompt library | Limited | Team | Advanced | Custom |
| AI usage controls | Basic | Standard | Advanced | Custom |
| Model routing | Limited | Limited | Advanced | Custom |
| Private context windows | Limited | Limited | Advanced | Custom |
| Diagnostic exports | Basic | Standard | Included | Custom |
| AI review queue | Limited | Team | Advanced | Custom |
| Governance controls | ||||
| Workspace roles | Basic | Team | Advanced | Custom |
| Workspace permissions | Basic | Team | Advanced | Custom |
| SSO | Limited | Limited | Advanced | Custom |
| Audit logs | Limited | 30 days | Unlimited | Custom |
| Data retention policy | Basic | Standard | Advanced | Custom |
| Environment secrets | Basic | Standard | Advanced | Custom |
| Deployment controls | Limited | Limited | Advanced | Custom |
| Domain controls | Limited | Limited | Advanced | Custom |
| SCIM | Limited | Limited | Limited | Custom |
| Legal hold | Limited | Limited | Advanced | Custom |
| Priority support | Basic | Standard | Priority | Custom |
| Workspace templates | Basic | Team | Advanced | Custom |
| Approval policies | Limited | Team | Advanced | Custom |
| Compliance exports | Limited | Limited | Advanced | Custom |
| Private deployment | Limited | Limited | Limited | Custom |
| Custom onboarding | Limited | Limited | Priority | Custom |
| Security review | Limited | Limited | Advanced | Custom |
| Admin analytics | Basic | Team | Advanced | Custom |
| Dedicated workspace controls | Limited | Limited | Advanced | Custom |
| Enterprise success plan | Limited | Limited | Limited | Custom |
Why teams switch
From context propagation to failure diagnosis, every layer is tuned for engineering speed, shared visibility, and trustworthy debugging.
10K+
test runs visualized
Keep every execution in one place, from urgent incident traces to long-lived regressions.
500+
teams collaborating
Shared workspaces, comments, and status streams keep engineering and QA aligned.
90%
faster debugging
Use context-aware history and AI explanations instead of manually replaying the chain.
100%
readable workflow files
.flow.md serves engineers, reviewers, and AI analyzers without extra translation layers.
Start building
Start with an open-source workflow foundation, then scale into team collaboration, execution history, and AI-powered diagnostics without changing tools.
Open-source at the core, with room for stronger governance as API teams grow.