Checks whether Remote can employ the given job title and role for this employment, and
returns the verdict without changing anything.

Call this before submitting contract details. The verdict tells you whether the
submission will succeed, be rejected, need a risk acknowledgement, or place the
employment into a human review; and the returned check_id lets the submission reuse
the verdict instead of recalculating it.

Calling this repeatedly with the same job title and role answers is cheap: the recorded
check is reused. Changing any of them produces a fresh verdict.

role_is_onsite and role_requires_license are answered here rather than in the
contract-details submission, which no longer asks for them and takes the returned
check_id instead. role_description stays part of contract details in its own right.

Authentication

This endpoint accepts any one of the following token types:

• Company-scoped access token (OAuth2AuthorizationCode) — obtained by a company manager through the Authorization Code flow or the Refresh Token flow. See Authentication for partners.
• Company-scoped access token (assertion) (OAuth2CompanyManagerAssertion) — obtained through the urn:ietf:params:oauth:grant-type:jwt-bearer grant for a company manager. See OAuth Assertion.
• Customer API token (CustomerAPIToken) — generated by the customer on their Integration Settings page, with the scopes they choose there. See Authorization for customers.

Scopes

Any one of the scopes in a token type's row is enough. all:write works too.