# Your openings. Your website.

Use the same company profile and openings anywhere. You control the layout, typography, and application experience.

## Start with public JSON

Published openings are readable without a key. Draft, closed and expired roles are excluded. Browser access is supported.

```js
const response = await fetch("https://rolefig.com/api/v1/companies/apex-works");
if (!response.ok) throw new Error("Openings unavailable");
const { company, jobs } = await response.json();
// Render jobs in your own components. Link to job.applyUrl.
```

- [Open Apex Works’ JSON feed](https://rolefig.com/api/v1/companies/apex-works)
- [Openings across every company (v2)](https://rolefig.com/api/v2/openings)
- [OpenAPI contract](https://rolefig.com/openapi.json)
- [Download the CLI](https://rolefig.com/downloads/rolefig-cli-0.10.0.tgz)

## Edit once, publish anywhere

Create your company workspace, verify your website, and publish a reviewed role. A company key lets your server or CLI manage the same roles. Credentials belong on your server, never in website JavaScript. Each write includes the revision you reviewed, so conflicting changes are caught.

```sh
rolefig publication apex-works --json
rolefig employer jobs --json
rolefig employer schema create-job
rolefig employer create-job ./role.json --json
rolefig employer publish-job ./review.json --json
# Private commands read ROLEFIG_API_TOKEN from the environment.
```

[Create your company workspace](https://rolefig.com/start). After verifying your website, create a scoped, expiring key under “Use your jobs on your website.”

## Works with your agent, too

rolefig’s public MCP server is read-only and needs no sign-in. Assistants can explore published companies and openings, and use the same checks as the [free tools](https://rolefig.com/tools).

```
https://rolefig.com/mcp
```

- **Claude:** add a custom connector with this URL. In Claude Code, run `claude mcp add --transport http rolefig https://rolefig.com/mcp`.
- **Cursor:** [add rolefig to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=rolefig&config=eyJ1cmwiOiJodHRwczovL3JvbGVmaWcuY29tL21jcCJ9).
- **VS Code:** add `{ "servers": { "rolefig": { "type": "http", "url": "https://rolefig.com/mcp" } } }` to `.vscode/mcp.json`.
- **Other clients:** `{ "mcpServers": { "rolefig": { "url": "https://rolefig.com/mcp" } } }`

Tools: `search_jobs` and `get_job` (real openings across companies), `list_published_companies`, `get_published_company` and `list_company_openings`. The demo catalog is separate: `demo_search_jobs`, `demo_get_job`, `demo_get_company` and `demo_list_companies` return illustrative roles whose applications are closed.

Use `/mcp/publisher` with your company key to manage roles. The private endpoint uses the same saved revisions and explicit review as the employer workspace. Your site keeps its own design.

Apex Works uses the shared publishing feed on MeetAPX while keeping its own guided application experience. Update openings here; candidates keep the familiar MeetAPX resume, questions and review steps.
