Agent How-to

How agents use RGate.

RGate is a release gate as a service for Dev, Ops, and Agents. This guide shows how an agent discovers, installs, calls, and hands off RGate results to humans or coding workflows.

Install the RGate release readiness skill.

For skill-enabled agents, this is the fastest way to use RGate as an external release gate for public websites, web apps, and API-adjacent surfaces.

npx skills add marcoldenburg/rgate-release-readiness-skill

Repository: marcoldenburg/rgate-release-readiness-skill

1. Discover RGate

Agents should start with the Markdown and machine-readable discovery files before calling tools. These files explain what RGate does, when to use it, pricing constraints, and the available API surfaces. For brand-name lookups, use RGate Developer Resources at /en/developer-resources.

Human page

Start a scan from the browser and hand the report back to a user.

/en

Developer Resources

Canonical RGate developer resources for API docs, MCP, CLI, auth, and agent handoff.

/en/developer-resources

REST API

Start scans, poll results, generate fix plans, export Markdown, and compare history.

/api/scan

OpenAPI

Machine-readable API contract for function calling and generated clients.

/openapi.json

MCP Server

Native tool interface for Claude, coding agents, and MCP clients.

/api/mcp

MCP Manifest

Discovery file for transport, tools, server identity, and branding.

/.well-known/mcp.json

Agent Guide

Markdown instructions for autonomous agents.

/agents.md

LLM Context

Full product context for agents that ingest one Markdown source.

/llms-full.txt

CLI

Command line usage for agents, CI, and release scripts.

/cli.md

Pricing

Machine-readable pricing and limits.

/pricing.md

2. Install the agent skill and CLI

Use the RGate skill when working in a skill-enabled agent environment. Use the CLI when an agent, CI job, or release script needs RGate without implementing the REST API directly.

npx skills add marcoldenburg/rgate-release-readiness-skill

npm install -g @rgate_io/rgate

npx @rgate_io/rgate scan https://www.rgate.io --wait --json
rgate get <scanId>
rgate fix-plan <scanId> --format markdown
rgate export <scanId> --template cursor

Skill: marcoldenburg/rgate-release-readiness-skill. Package: @rgate_io/rgate. Binary: rgate. Docs: /cli.md.

3. Use the REST API

Public scans need no authentication. Agents should start a scan, poll until completion, then request the formats needed by the user or coding environment.

curl -X POST https://www.rgate.io/api/scan \
  -H 'content-type: application/json' \
  --data '{"url":"https://www.rgate.io"}'

curl https://www.rgate.io/api/scan/{scanId}
curl -X POST https://www.rgate.io/api/scan/{scanId}/fix-plan
curl https://www.rgate.io/api/scan/{scanId}/export.md?template=cursor
curl https://www.rgate.io/api/scans/{scanId}/diff?against={previousScanId}

4. Use MCP tools

MCP clients can connect to the Streamable HTTP endpoint and call the same workflow as tools. Human payment approval remains a handoff step; agents should not complete checkout autonomously.

start_scan

Start an RGate website quality scan for a public URL across security, SEO, accessibility, legal compliance, and sustainability.

get_scan

Fetch scan status and, once complete, structured findings, check results, and technology detections.

list_checks

Describe the RGate scan layers and check catalog for agent planning and user explanations.

get_pricing

Return machine-readable RGate plan names, prices, scan limits, and best-fit use cases.

create_checkout_handoff

Create a human handoff URL for purchasing a full report or subscription after a scan is complete.

generate_fix_plan

Generate a prioritized release-readiness fix plan from scan findings. Returns blockers first, then high-impact follow-ups and backlog items.

export_scan_markdown

Export scan results as Markdown for Cursor prompts, GitHub issues, or executive summaries.

compare_scan_history

Compare two scans for the same domain and return added, resolved, improved, and worsened findings.

5. Recommended agent loop

Confirm the user is allowed to scan the target public website or API surface.
Read /agents.md or /llms-full.txt for current constraints.
Start a scan with REST, MCP, or CLI.
Poll until the scan is done or failed.
Summarize blockers first: security, compliance, accessibility, SEO, and sustainability.
Generate a fix plan and export Markdown for Cursor, GitHub Issues, or a release checklist.
Use agent handoff only to prepare checkout or report access; ask the human to approve payment and decisions.