Onboard an international contractor via the Remote.com API and configure recurring payments
domain: developer.remote.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth2 access token using the client_credentials flow against https://gateway.remote.com/auth/oauth2/token
Create a contractor employment record via POST /v1/employments specifying contractor as the employment type and providing contract terms, rate, and currency
Retrieve and complete the onboarding form fields required for the contractor's country, then mark onboarding complete
Once the contractor completes their side of onboarding, configure invoice or payment schedule settings via the Remote platform or API
Monitor payment status via Remote webhooks or by polling the employment and invoice endpoints
Handle currency and FX considerations: Remote processes payments in the contractor's local currency; confirm supported currencies in the Remote documentation
Known gotchas
Contractor and EOR employee records both use POST /v1/employments but with different required fields and onboarding forms — misclassifying the employment type causes compliance and tax issues
Remote's access token expires in 3600 seconds; build token refresh into your HTTP client middleware to prevent payment flows from being interrupted mid-execution
Some countries have restrictions on contractor engagements (e.g., misclassification risk thresholds); Remote surfaces compliance warnings via the API — do not suppress these warnings
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?