Settings

Choose your AI provider and check which features are available.

Feature availability

Check whether AI drafting, account storage, email and browser assistance are available.

Oct 10, 6:15 PM

Browser Rendering

Ready

BROWSER binding detected for PDF export and reviewed browser checks.

Outbound email

Needs setup

RESEND_API_KEY is not configured; email sends fail closed and are skipped.

Next: Set the Resend secret in the Worker environment when production sending is ready.

Sender identity

Code ready

Using the default sender RolePatch <alerts@rolepatch.com>.

Next: Override EMAIL_FROM if sender verification uses a different production identity.

AI runtime

Ready

Free AI gateway service binding is configured for managed inference.

Knowledgebase similarity

Needs setup

Semantic pre-ranking needs the shared Knowledgebase service key and a RolePatch RAG index.

Next: Configure RAG_SERVICE_KEY and ROLEPATCH_RAG_INDEX_ID, then add the RAG_SERVICE binding when production config changes are approved.

Auth and OAuth

Ready

Better Auth and Google OAuth configuration is present.

Payment checkout

Needs setup

Dodo checkout needs an API key, return URL, and starter/pro/bulk product IDs.

Next: Configure DODO_PAYMENTS_API_KEY, DODO_PAYMENTS_RETURN_URL, and all DODO_PRODUCT_* IDs.

Payment webhook

Needs setup

Dodo webhook verification needs the webhook secret and token product IDs.

Next: Configure DODO_PAYMENTS_WEBHOOK_KEY and all DODO_PRODUCT_* IDs before accepting live payments.

Worker hooks

Code ready

Scheduled and Email Routing handlers are wired in worker.mjs and dispatch through internal routes.

Next: Activate production cron triggers and the Email Routing rule in Cloudflare when ready.

Chrome extension

Store-ready package checks for reviewed ATS fill and receipt capture.

Unpacked build

Package

pnpm --dir extension build

Load path

extension/dist

API base

https://rolepatch.com

Auth

Signed-in browser profile

ATS coverage

GreenhouseLeverWorkdayAshbyWorkableRecruiteePersonioSmartRecruiters

Boundary

Uses active-tab access and provider host permissions. No all-site permission, captcha bypass, or unattended bulk apply.

Connect your resume API

Send a job description or a public job reference and get a complete resume from your saved master. With one master, you can omit its ID; with several, choose a profile using the MCP tools.

Access can read your saved master profiles, use credits to generate resumes, and save versions to Jobs History. It expires within 24 hours, or sooner if you sign out of this session. It cannot submit applications.

Sign in with Google from the account menu to connect saved resumes. Guest API calls can still supply a master as resume_markdown.

Use Authorization: Bearer <your token> with:

POST https://rolepatch.com/api/resume

Send jd_text and, if needed, resume_id. The response contains markdown and a History link. Add format: "html" for HTML too.

For the stdio MCP bridge, set ROLEPATCH_API_TOKEN in secure client configuration. For assistants that support OAuth, add this server URL and choose OAuth:

https://rolepatch.com/api/mcp

Sign in with Google and approve resume access when your assistant opens RolePatch. Each connection uses your saved master; MCP saves to History only when requested.