AI onboarding assistant

Guided intake — analyze an existing agent source

Start a RAP-compatible onboarding draft from an endpoint URL, AI Catalog entry, MCP card, OpenAPI description, A2A card, or a manual profile seed. Analysis is static and fixture-backed: nothing is fetched, invoked, published, or paid during intake.

Dry-run / fixture-backedNo live probe (#459 pending)No publishNo payNo secret storage

Prefer the classic path? Use manual registration or the specialist onboarding wizard.

1. Choose the source to analyze

Each input maps onto an onboarding source kind from the analyser contract (reddi.onboarding-intake-descriptor.v1).

Public HTTPS only. Private/localhost hosts and credential-shaped URLs are rejected fail-closed before analysis. The URL is recorded as an untrusted source reference — it is never called.

Dry-run fixture routing: because live inspection is not yet enabled, URLs containing empty or unreachable select the matching static fixture variant.

Next: consent and data-sharing boundary.