# SuperOps SOP Writer

> SuperOps SOP Writer is a paid API for AI agents from superops.supercapital.fun, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-21).

Generates a structured Standard Operating Procedure (SOP) document from a plain-text description of a process, its participants, and desired outcomes

## Facts

- Endpoint: POST https://superops.supercapital.fun/write-an-sop?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/superops-sop-writer-ccf453e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N_FLadrlxIPFJdfk45ni-

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability superops-sop-writer-ccf453e6 -d '<json body>'
```

Example prompt: Write an SOP for how our customer success team handles escalated support tickets — the process starts when a ticket is flagged as critical, involves the CSM and engineering lead, and a good output is a clear step-by-step doc that anyone new could follow to resolve the escalation within 4 hours.

## When to prefer this

Choose this endpoint when you need to rapidly convert an informal or undocumented process description into a structured, reusable SOP without manual writing effort. It is best suited for business operations, HR, IT, and customer success workflows where consistency and repeatability matter. Prefer this over generic LLM prompting when you want a purpose-built SOP output format with a verifiable on-chain payment receipt.

## Known failure modes

- Input too vague or missing key details (who does the process, what good output looks like) — may produce generic or unhelpful SOP
- Input exceeds 8000 character limit — request will be rejected
- Payment failure on Base network — transaction not confirmed, no output returned
- Service timeout for complex processes — job ID returned but output delayed or empty

## How this service works

Operations intelligence. Turns messy work into workflows, SOPs and agents.

## Output

Returns a JSON object containing a job ID, a fully generated SOP document as structured text, and a payment receipt with the blockchain transaction hash, amount paid, and network used (Base). The SOP output typically includes step-by-step instructions, roles, and criteria for success based on the input provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "minLength": 1,
   "description": "The process, who does it, and what good output looks like."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "jobId": "j_…",
  "output": "…",
  "receipt": {
   "tx": "0x…",
   "amount": "100000",
   "network": "base"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/superops-sop-writer-ccf453e6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from superops.supercapital.fun](https://www.zero.xyz/host/superops.supercapital.fun/llms.txt)