SilkyDocs
Sign in

Silky for AI agents

Silky is a hiring system designed to be driven by an AI agent, not a human clicking a dashboard. You can sign up a customer, create a job, post it to a careers page, process applicants, and deliver a shortlist - all via HTTP or MCP, with no UI involvement.

This page exists so a Claude Code session (or any LLM) can read it once and have everything needed to operate Silky for a customer.

TL;DR (2 minutes)

  1. Create an account: POST /api/v1/accounts/signup with an email. You get back a trial_api_key (prefix sk_trial_).
  2. Put the key in an Authorization: Bearer ... header on every subsequent request.
  3. Create a job from plain text: POST /api/v1/jobs/from-description.
  4. Post it: POST /api/v1/job-ads and fetch share_links to distribute.
  5. Applications arrive, get auto-parsed and auto-assessed. Poll GET /api/v1/applications?status=longlisted or subscribe to webhooks.
  6. Move a candidate forward: POST /api/v1/applications/{id}/transition.

That is the whole loop. Everything else on this site drills into one of those steps.

Two ways to drive Silky

REST (recommended for agents running on your own infra): standard HTTP, any language, OpenAPI spec at /api/v1/openapi.json. See the full reference at /docs.

MCP (recommended for Claude Desktop, Claude Code, or any MCP-aware client): Silky exposes 27+ tools over MCP at https://app.silky.so/api/mcp. OAuth metadata at /.well-known/oauth-protected-resource. See MCP quickstart.

Both surfaces have the same capability. Pick the one that fits how the agent is being hosted.

Pages

  • MCP quickstart - connect Claude Desktop or Claude Code, first tool call, JSON config block.
  • Sign up a customer - programmatic account creation, in curl / JS / Python.
  • Top 10 tasks - runnable examples for the ten things agents do 95% of the time.
  • Error handling - request IDs, retry rules, idempotency keys, rate limits.
  • Webhooks - subscribe, verify signatures, event catalogue.

Honest limits

Things Silky does not do yet. Build around them or use another tool:

  • No native background-check integration. Use a partner (Checkr, etc.) and store the result as a timeline event via the API.
  • No in-app payroll/HRIS push on hire. You get a hire.created webhook; wire up your own downstream.
  • Free tier is rate-limited. If your agent is going to burst, ask for a paid key before you ship.
  • The MCP server requires OAuth for write operations. Read-only tool use works with the trial API key over HTTP; MCP writes need the OAuth flow.

Canonical host

All examples in this section use https://app.silky.so as the host. If you are developing locally, replace it with http://localhost:3001.