Is there a Job Opportunities API MCP server?

You don't need an MCP server to give your agent the Job Opportunities API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent searches listings, closed roles, and employers as it needs them. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

Can I limit what my agent is allowed to do with the Job Opportunities API?

Yes. For example, write a rule that allows only the listing search and single-listing read operations, so a candidate-facing agent can find and read jobs but cannot run bulk exports or queue export packs that draw on your plan's allowance. Because the employer slug is in the path at /v1/companies/{slug}, a rule can also hold an agent to one company's profile, and every call is logged.

How do I find only jobs that are confirmed remote with the Job Opportunities API?

Add remote_confirmed=true to the listing search. Each job's field_sources names every field as published, inferred, or absent, and this filter returns only listings whose remote status the source itself stated rather than one derived by the API.

What are the rate limits for the Job Opportunities API?

The Job Opportunities OpenAPI spec defines a rate-limited response that reports the limit hit in records per month, requests per day, or requests per minute, but it does not publish the numbers. Call GET /v1/me to read your key's plan and quota, and check https://jobopportunitiesapi.org for plan details.

How do I search job listings with the Job Opportunities API through Jentic?

Search Jentic for an intent like 'find remote jobs in a country', import the Job Opportunities API from the API Directory, and store your bearer token once. Your agent then calls GET /v1/jobs with filters such as country and title, passing next_cursor back as cursor to page. To run it on your own infrastructure, install Jentic One from its GitHub repo.