# Your hiring pipeline. One clear summary.

Source: https://corespeed.io/integrations/ashby

Connect Ashby to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists open jobs, candidates, applications, scheduled interviews and offers, and drafts a pipeline summary for the hiring team. Access follows the endpoint permissions on your Ashby API key, and moving a candidate, adding a note or approving an offer is a separate call.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Ashby after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Know where each candidate is. See who is waiting

Ask your agent for the state of a role: who is at which stage, what is scheduled, and who has waited too long.

You ask your agent: "Review the open Backend Engineer job in Ashby. List candidates by stage, the interviews set for this week, and anyone waiting more than five days. Do not move anyone."

It calls CoreSpeed:

- `ashby__job_list`: ok, 341 ms
- `ashby__application_list`: ok, 512 ms
- `ashby__interviewSchedule_list`: ok, 406 ms

It reads from: Ashby.

### Pipeline summary: Backend Engineer, this week.

Two candidates are at onsite with interviews set. One has waited six days at screen without a next step.

**On track**

- Jessica, system design on Tuesday.
- Stewart, team fit on Thursday.

**Follow up**

- Parker has waited six days at screen. Schedule a call or close the loop.

_Illustrative example · Fictional candidates · No stage changed_

All connectors: https://corespeed.io/docs/connectors

## From candidates to the next decision

Requests you can make once Ashby is connected. The data is fictional.

### See the pipeline by stage

Backend Engineer · pipeline · Applications by stage

- Onsite: 2 candidates
- Waiting: 1 candidate for 6 days
- From the jobs your key can read

### Prepare the interview week

This week's interviews · Scheduled interviews

- Tuesday: Jessica, system design
- Thursday: Stewart, team fit
- Read only

### Hold the offer for a person

An offer approval · Approvals

- Offer: Jessica, Backend Engineer
- Rule: Ask before approving an offer
- Waiting for you

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Ashby**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Which Ashby data can the agent read?

Only the endpoints your Ashby API key allows. Ashby grants read or write per module, so a read-only key keeps the agent from changing anything.

### Can the agent move a candidate or approve an offer?

Only with a key that allows writes. Each change is a separate tool call, and approvals can hold it for a person. How approvals work: https://corespeed.io/docs/approvals

### Does this replace Ashby?

No. Ashby stays where your team runs hiring. CoreSpeed brings its pipeline into the agent you already use.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/ashby

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [BambooHR for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/bamboohr): Ask your agent who is out, which time-off requests are waiting, and what a saved report says. It sees only what your BambooHR user can.
- [Calendly for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/calendly): See your Calendly events and invitees inside your agent, and prepare for the day's calls. Cancelling stays a separate step.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Ashby API: authentication and permissions: https://developers.ashbyhq.com/docs/authentication

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)