mercury-onboarding-apply
Mercury Onboarding Apply
Walk a user through starting a Mercury onboarding application. This skill generates a blank, annotated apply.yaml template with mercury apply --template, fills it out with the applicant's business and beneficial-owner details, confirms the summary with the user, and submits it by piping the file into mercury apply. On success the API returns a signupLink the user opens in the browser to finish.
Auth is handled by the CLI per mercury-shared (MERCURY_API_KEY or mercury login). This skill never constructs auth headers. Note that mercury apply --template needs no auth and makes no API call — only the final submit does.
COMPLIANCE — DO NOT FABRICATE KYC DATA. Onboarding is a Know-Your-Customer / Know-Your-Business flow. Identity, ownership percentages, EIN/Tax ID, legal names, dates of birth, SSNs, and addresses must come from the user. NEVER guess, infer, auto-fill, or "reasonable-default" any of these fields. For any field that is missing, ambiguous, or low-confidence, STOP and ask the user. Submitting fabricated identity or ownership data is a real legal/compliance problem, not a formatting nit. Treat this the way mercury-receipt-upload treats an irreversible upload — but stricter.
Parameters
| Parameter | Default | Description |
|---|---|---|
templatePath |
apply.yaml (cwd) |
Where to write the blank template and the filled application. |
applicantDetails |
(required) | The business + beneficial-owner information, supplied by the user. Never synthesized. |