SOP Doc
See how things work. Define processes as .osop files. Browse them visually. Understand any API, team, or company at a glance.
API Doc shows each endpoint. SOP Doc shows the sequence — which steps, in what order, who is involved, what data flows between them. Non-engineers can read it too.
The Loop
Make things better. Execute workflows, record what happened, let AI write a better version. Each cycle gets faster, cheaper, more reliable.
.osoplog records every step: duration, cost, tools, AI reasoning, human decisions. Feed logs to osop synthesize. AI reads the patterns. You get an optimized .osop. Repeat.
See it in action
OSOP uses its own format to explain itself. Click Visual to see the flow. Click .osop to see the YAML.
Stripe Payment Flow (API SOP)
Create a Stripe customer with email and metadata.
Create a payment intent. Amount, currency, customer ID.
Confirm the payment with a payment method.
Verify the payment succeeded.
AI generates a personalized receipt email.
The Optimization Loop
Execute the workflow. Agent nodes call LLMs. API nodes send HTTP requests.
Every node: timestamps, duration, cost, tools, AI reasoning, human decisions.
Feed multiple .osoplog to AI. It writes an optimized .osop.
Compare old vs new. Per-step duration, cost, status changes.
Accept, modify, or reject. The human decides.
Everything serves the two pillars
CLI, editor, SDKs, converters, MCP server, agent integrations. All open source.
SOP Doc
“It started with wanting to know what the AI did. Then I realized every team has the same problem — processes are invisible. Every API sequence, every company workflow, every human-AI collaboration. If you can't see it, you can't improve it. OSOP makes it visible.”
— Why OSOP exists