Async Interview for AI agents
Async Interview is an on-demand video interview platform where candidates record answers to preset questions, letting hiring teams review responses on their own schedule instead of live calls. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Async Interview.
Review candidate interview responses
List the recorded video responses candidates submitted for a specific job posting.
Update a job posting's details
Update the interview questions or settings tied to a specific job posting.
Confirm before deleting a job
Deleting a job posting removes it entirely, so it should be confirmed before it happens.
4 Async Interview actions, graded by risk.
Every Async Interview action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- async_interview.list_jobsList Jobs
- async_interview.list_interview_responsesList Interview Responses
write
1Create and change things. Allow, or ask the user first.
- async_interview.update_jobUpdate Job
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- async_interview.delete_jobDelete Job
Async Interview in three steps.
- 01Your users connect Async InterviewThey add their Async Interview api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Job” can wait for the user, and “delete Job” can be denied outright.
- 03Any agent can actYour agent calls Async Interview through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('async_interview', { read: 'allow', write: 'ask', // update_job destructive: 'deny', // delete_job }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Async Interview connects.
Users add their Async Interview api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Async Interview connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Async Interview from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Async Interview and Arc0, answered.
Can I use Async Interview with Claude, ChatGPT or Cursor?
Yes. Connect Async Interview to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Async Interview actions you allow.
How do users connect Async Interview?
Users add their Async Interview api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Async Interview actions can my agent take?
4 in total: 2 read, 1 write and 1 destructive, such as “update Job”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Async Interview?
Yes. Actions like “delete Job” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Async Interview too?
Yes. The same Async Interview connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Async Interview into your agent.
Your users connect Async Interview once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan