Your API keys
Our loop. Your credentials.
Parsemend runs the fix-run state machine — context bundles, confidence gating, resumable steps — using your own provider credentials. Anthropic, OpenAI, Gemini, or a self-hosted Ollama endpoint. Inference is billed to your provider account at raw token prices, never marked up by us.
The four questions
- Where the run executes
- Parsemend
- Who pays for tokens
- You, directly to your provider
- Model choice
- Anthropic · OpenAI · Gemini · Ollama
- Source seen by Parsemend
- Streamed, never stored
How the data flows
Parsemend drives the state machine and assembles the context bundle, which transits to your provider under your credentials. The bundle is not retained.
- Your infrastructure
- source code
- Parsemend
- error eventsfix queuefix run
- Model provider
- model call
What Parsemend contributes
Context bundles
The stack trace, the in-app frames, the surrounding source, the breadcrumbs and the recent commits that touched those lines — assembled into one payload an agent can act on without crawling the repo.
Fix-run state machine
Root cause, then solution, then coding, then change description. Each step is a checkpoint. A run that dies at step three resumes at step three rather than starting over.
Confidence gating
Every step emits a confidence score. Below the project's threshold the run pauses and waits for a human instead of confidently shipping a wrong patch.
Draft PR post-back
The patch arrives as a draft pull request against the right branch, with the root cause and the reasoning in the description. It never merges itself.
Who this is for
Teams who want the orchestration without operating an agent, and who already have provider accounts.