# Obol Deploy Config Generator

> Obol Deploy Config Generator is a paid API for AI agents from api.obol.sh, paid per call via x402, $5/call, status unknown (last checked 2026-10-13).

Generates GitHub Actions CI/CD and deployment configuration files for a repo and opens a pull request on GitHub targeting the specified platform (Vercel, Cloudflare, or Railway).

## Facts

- Endpoint: POST https://api.obol.sh/deploy?utm_source=zero.xyz
- Price: $5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-deploy-config-generator-8af3e00e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WnAtSlr0XKE3cFhZ5uOP7

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 obol-deploy-config-generator-8af3e00e -d '<json body>'
```

Example prompt: Can you set up a GitHub Actions CI/CD pipeline and deployment config for my repo acme-org/my-app targeting Vercel, and open a pull request against the main branch? Notify me at dev@acme.com when the PR is ready.

## When to prefer this

Choose this endpoint when a user wants to automatically generate CI/CD pipeline and deployment configuration files (GitHub Actions workflows, platform-specific config) for an existing GitHub repository and have them delivered as a pull request. Ideal when the target platform is Vercel, Cloudflare, or Railway and the user wants a zero-setup automated approach rather than writing YAML manually.

## Known failure modes

- Invalid or inaccessible GitHub repo — repo not found or insufficient permissions
- Unsupported platform value — must be one of vercel, cloudflare, or railway
- Payment failure — $5 USDC charge declined or x402 protocol error
- GitHub API rate limit or fork creation failure
- Branch not found — specified branch does not exist in the repo
- PR creation failure — duplicate PR already open for same branch

## How this service works

Obol: Repo → GitHub Actions CI/CD + deploy config → GitHub PR — $5 USDC

## Output

Returns the URL of the opened GitHub pull request, the URL of the forked repository used to stage the changes, a list of file paths written to the branch (e.g. .github/workflows/deploy.yml), and the name of the branch containing the changes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo",
  "platform"
 ],
 "properties": {
  "repo": {
   "type": "string",
   "description": "GitHub repo in owner/repo format"
  },
  "email": {
   "type": "string",
   "description": "Email address to notify when PR is ready"
  },
  "branch": {
   "type": "string",
   "description": "Branch to base the PR on (defaults to repo default)"
  },
  "platform": {
   "type": "string",
   "description": "Deploy target platform: vercel, cloudflare, or railway"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "pr": {
  "type": "string",
  "description": "URL of the opened pull request"
 },
 "fork": {
  "type": "string",
  "description": "URL of the forked repository"
 },
 "files": {
  "type": "array",
  "description": "File paths written to the branch"
 },
 "branch": {
  "type": "string",
  "description": "Branch name on the fork"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-deploy-config-generator-8af3e00e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.obol.sh](https://www.zero.xyz/host/api.obol.sh/llms.txt)