# AgentWeb Skill: Workflow Mapping

Use AgentWeb workflow mapping when a company wants an AI agent to discover, recommend, quote, book, submit, pay, verify, or complete a repeated business workflow through a scoped Agent Map.

## When to use

Use this skill when a business owner or coding agent asks to install AgentWeb, make a repo usable by agents, publish agent-readable action metadata, or turn a repeated business workflow into a callable Agent Map.

## When not to use

Do not use this skill for one-off scraping, unsafe account access, raw card handling, or workflows where the business already has a complete first-party API that agents can call directly.

## Inputs

- Business domain and customer-approved workflow goal.
- Public docs, forms, API specs, payment terms, support policies, and verification requirements.
- Allowed actions, disallowed actions, auth model, payment authority, rate limits, and rollback path.

## Outputs

- Endpoint map with method, URL, required fields, auth state, payment state, success proof, failure classes, and retry rules.
- OpenAPI, MCP, A2A, SDK, or LangChain-callable surface for approved workflows.
- Verification artifact contract for receipts, status pages, signed setup proof, and failure evidence.

## Boundaries

Do not collect credentials, raw prompts, private page bodies, card data, bank data, or unrestricted API keys. Paid workflows require scoped payment authority before checkout or execution.