[Integrations](https://spiral.ai/integrations) › [Codex](https://spiral.ai/integrations/codex) › [Ashby job details](https://spiral.ai/integrations/codex/ashby-job-details)

# How to Use Ashby job details in Codex

Returns one posting's description, compensation tiers, application link, and deadline when supplied, plus application questions on request. Use it to inspect requirements and application preparation after finding a role.

|  |  |
| --- | --- |
| Model | Ashby job details |
| Available through | Alexandria |
| Category | Lead Gen |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Ashby job details in Codex

- Use Ashby job details for a current engineering posting linked from https://jobs.ashbyhq.com/ashby and add its description and application link to this project's role detail view.
- Use Ashby job details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from Ashby job details and tell me what changed since last week.
- Check Ashby job details and summarize what you find in three bullet points.
- Pull the newest data from Ashby job details and give me the result as a table.

## How to set up Ashby job details in Codex

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the hosted server**

```bash
codex mcp add spiral --url https://api.spiral.ai/mcp
```

2. **Sign in**: Codex opens the browser: sign in to Spiral and click Authorize. No API key. `codex mcp list` then shows Spiral.

```bash
codex mcp login spiral
```

### Use the Spiral skill

1. **Send Codex this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Ashby job details**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "ashbyhq-com/jobs/job",
    "input": {
      "board": "<board>"
    }
  }'
```

Then paste one of the prompts above: Codex finds Ashby job details on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/codex

## Ashby job details tools and prices

- [Ashby job boards · Job](https://spiral.ai/tools/alexandria/ashbyhq-com/jobs/job) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | A pasted posting URL https://jobs.ashbyhq.com/<board>/<job_id> or its /application form page (query strings are ignored; an /application URL turns on application_form). Exactly one of url or board+job_id. Pattern: ^https?://. |
| board |  | — | The employer's Ashby board slug: the path segment of https://jobs.ashbyhq.com/<board> (e.g. ashby, openai). Case-insensitive. Pattern: ^[A-Za-z0-9][A-Za-z0-9._-]{0,99}$. |
| job_id |  | — | Posting UUID from jobs items[].id or the /<board>/<job_id> path. Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$. |
| application_form |  | — | Also return the application form's questions (one more request). Defaults to true for a pasted /application URL, false otherwise. |

## What can you do with Ashby job details in Codex?

Build an employer hiring view from Ashby's public board data. Organize company and team context alongside current postings, with individual role details available for closer inspection.

### Employer hiring briefs

Combine employer identity and team structure with current openings and selected role descriptions. Produce a company brief that links hiring observations to specific postings.

### Public hiring change reports

Compare saved employer overviews, opening lists, and role details to identify changes in posting counts, team coverage, and published requirements.

### Career page content audits

Review employer board descriptions and team names alongside listing metadata and individual descriptions. Flag inconsistent terminology or role information for the employer to review.

### Department hiring comparisons

Use each employer's team structure to organize openings, then read selected descriptions to compare the work being advertised. Report posting totals without treating them as planned headcount.

### Location and workplace research

Compare advertised locations and workplace classifications across openings. Read individual descriptions to explain the geographic restrictions stated for selected roles.

### Published compensation comparisons

Collect the compensation information attached to comparable openings and inspect the tiers for selected postings. Keep the employer's published ranges attached to the roles they describe.

### Application preparation checklists

Find suitable openings, read their requirements, and inspect the application questions for selected postings. Turn the published information into a checklist of materials to prepare.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Codex guides](https://spiral.ai/integrations/codex)

## Ashby job details in other agents

- [Amp](https://spiral.ai/integrations/amp/ashby-job-details)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/ashby-job-details)
- [Claude](https://spiral.ai/integrations/claude-desktop/ashby-job-details)
- [Claude Code](https://spiral.ai/integrations/claude-code/ashby-job-details)
- [Cline](https://spiral.ai/integrations/cline/ashby-job-details)
- [Cursor](https://spiral.ai/integrations/cursor/ashby-job-details)
- [Devin](https://spiral.ai/integrations/devin/ashby-job-details)
- [dots](https://spiral.ai/integrations/dots/ashby-job-details)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/ashby-job-details)
- [Gemini](https://spiral.ai/integrations/gemini/ashby-job-details)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/ashby-job-details)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/ashby-job-details)
- [goose](https://spiral.ai/integrations/goose/ashby-job-details)
- [Grok](https://spiral.ai/integrations/grok/ashby-job-details)
- [Grok Build](https://spiral.ai/integrations/grok-build/ashby-job-details)
- [Hermes](https://spiral.ai/integrations/hermes/ashby-job-details)
- [Instinct](https://spiral.ai/integrations/instinct/ashby-job-details)
- [Manus](https://spiral.ai/integrations/manus/ashby-job-details)
- [Muse](https://spiral.ai/integrations/muse/ashby-job-details)
- [Muse Code](https://spiral.ai/integrations/muse-code/ashby-job-details)
- [n8n](https://spiral.ai/integrations/n8n/ashby-job-details)
- [Notion](https://spiral.ai/integrations/notion/ashby-job-details)
- [OpenClaw](https://spiral.ai/integrations/openclaw/ashby-job-details)
- [opencode](https://spiral.ai/integrations/opencode/ashby-job-details)
- [Perplexity](https://spiral.ai/integrations/perplexity/ashby-job-details)
- [Raycast](https://spiral.ai/integrations/raycast/ashby-job-details)
- [VS Code](https://spiral.ai/integrations/vscode/ashby-job-details)
- [Windsurf](https://spiral.ai/integrations/windsurf/ashby-job-details)
- [Zapier](https://spiral.ai/integrations/zapier/ashby-job-details)

## More Codex guides

- [Ashby job board overview](https://spiral.ai/integrations/codex/ashby-job-board-overview)
- [Ashby job listings](https://spiral.ai/integrations/codex/ashby-job-listings)
- [Arizona ROC license scope description](https://spiral.ai/integrations/codex/arizona-roc-license-scope-description)
- [AusTender contract notice details](https://spiral.ai/integrations/codex/austender-contract-notice-details)
- [Arizona ROC license classifications](https://spiral.ai/integrations/codex/arizona-roc-license-classifications)
- [AusTender contracts by date](https://spiral.ai/integrations/codex/austender-contracts-by-date)

## Questions about Ashby job details in Codex

**Can Codex use Ashby job details?**

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run Ashby job details like any built-in tool.

**How much does Ashby job details cost in Codex?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Codex plan is separate.

**Do I need an Alexandria account to use Ashby job details in Codex?**

No. Spiral runs Ashby job details on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up Ashby job details in Codex?**

About two minutes: add the hosted server, then sign in.

**Does Codex wait while Ashby job details runs?**

Ashby job details runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.

**Does Ashby provide a history of closed postings?**

Ashby's public Posting API is documented for currently published postings. For comparisons over time, collect your own snapshots of employer boards and postings.

**Does the publish date show when a role first appeared?**

The timestamp records when the posting was last published. It should not be used as proof of the role's original creation date.

**Does a remote flag mean fully remote?**

Ashby's remote boolean covers both remote and hybrid postings. Use the workplace classification to distinguish fully remote work from a hybrid arrangement.

**Does the posting count equal the number of hires?**

An employer can publish multiple postings for one underlying job. Treat board totals as posting counts, rather than a measure of distinct roles or planned hires.

**Can a posting be accessible without appearing on the employer's board?**

Yes. An unlisted posting can remain published and accessible by direct link while being absent from the main board; Ashby instructs integrations not to display those postings publicly.

