$ man deploy-config-risk
/deploy-config-risk
PRICE / CALL
$0.02
USDC · base mainnet · scheme: exact
──────────────────────────────────────────────────────────────────────────────
NAME
deploy-config-risk — audits deploy configuration files for production risks
SYNOPSIS
POST https://x402.agentutility.ai/deploy-config-risk
Content-Type: application/json
X-PAYMENT: <signed-transferWithAuthorization>
{ ... }↳ first call → 402 Payment Required. Sign USDCtransferWithAuthorization, retry with theX-PAYMENT header.
DESCRIPTION
Audits deploy configuration files for production risks. Fetches Dockerfile, wrangler.toml, vercel.json, netlify.toml, fly.toml, docker-compose.yml, and serverless.yml and flags open CORS with credentials, exposed admin ports (22/5432/6379/etc), plaintext secrets in inline env, dev/debug mode left enabled, and missing healthchecks. Returns 0-100 score, per-finding kind/severity/path/line/redacted-evidence/recommendation, and a Venice plain-English verdict. Dual input: {repo: 'owner/name'} for public GitHub or {files: [{path, content}, ...]} for private / agent-workspace use. Use it as a Dockerfile lint, vercel.json hardening pass, wrangler.toml review, docker-compose.yml safety check, fly.toml secrets check, netlify deploy gate, open CORS detector, exposed admin port detector, plaintext-secret-in-env detector, or production-readiness deploy gate.
OUTPUT — response shape
| field | type | description |
|---|
| score | number | Risk score from 0-100 where higher means safer deploy config; aggregates all finding severities. |
| risk_level | string | Risk bucket like 'low', 'medium', 'high', or 'critical' derived from the score and worst findings. |
| findings | array | Array of issues with kind, severity, file path, line number, redacted evidence, and recommendation per item. |
| signals | object | Object of detected config signals like open_cors, exposed_ports, plaintext_secrets, debug_mode, missing_healthcheck. |
| summary | string | Venice plain-English verdict summarizing the deploy config's production-readiness and top risks. |
| metadata | object | Run metadata including files scanned, file types detected, repo or input mode, and audit timestamp. |
EXAMPLES — two ways to call
EXAMPLE 1 · curl
curl -X POST https://x402.agentutility.ai/deploy-config-risk \
-H 'Content-Type: application/json' \
-d '{ }'first response = 402 Payment Required with payment requirements; sign + retry with X-PAYMENT.
EXAMPLE 2 · mcp
# Install the MCP package for this endpoint's cluster
npx -y @agentutility/mcp-<cluster>
# Required: EVM private key with USDC on Base
export X402_PRIVATE_KEY=0x...
# Then call the deploy-config-risk tool from your MCP-aware agent.
MCP server handles payment automatically — your coding agent just calls the tool by name.
METADATA
- tags
- securitydeploydockerfilecorssecretsprooflayer
- env
- VENICE_API_KEY
- methods
- POST
- cluster
- prooflayer
- price
- $0.02 USDC per call
ADJACENT — other endpoints in prooflayer
agentutility(7)