# PR Triage by Cult OS

> PR Triage by Cult OS is a paid API for AI agents from www.cultos.dev, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-13).

Analyzes a pull request and triages it by summarizing changes, assessing risk, and categorizing the PR for review prioritization

## Facts

- Endpoint: POST https://www.cultos.dev/services/pr-triage
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pr-triage-by-cult-os-87314269
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KWcYgrETb1GculqPbVSY3

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 pr-triage-by-cult-os-87314269 -d '<json body>'
```

Example prompt: Can you triage this pull request for me and tell me how risky it is and what it changes? Here's the PR: https://github.com/myorg/myrepo/pull/42

## When to prefer this

Choose this endpoint when you need automated, AI-driven triage of individual pull requests — especially in workflows where engineering teams want to prioritize review queues, surface risky changes early, or onboard contributors efficiently. It is purpose-built for PR analysis rather than general code review or vulnerability scanning (use the Vulnerability Audit endpoint for security-focused analysis).

## Known failure modes

- Invalid or inaccessible pull request URL returns an error
- Private repository PR without proper access credentials may fail to fetch
- Malformed pullRequest input field results in a validation error
- Very large PRs with many files may produce incomplete or truncated analysis
- Rate limits or upstream failures may cause timeouts

## How this service works

PR Triage by Cult OS

## Output

A structured triage report for the pull request, including a summary of changes, a risk level assessment, a category label (e.g. bug fix, feature, refactor, chore), and recommended review priority to help engineering teams manage their code review workflow efficiently.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pullRequest": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "00000000-0000-4000-8000-000000000000",
  "status": "queued",
  "service": "pr-triage",
  "statusUrl": "/services/jobs/00000000-0000-4000-8000-000000000000"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pr-triage-by-cult-os-87314269/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.cultos.dev](https://www.zero.xyz/host/www.cultos.dev/llms.txt)