Point your AI agent at DYNIK
DYNIK treats an AI agent as a first-class user. Create a scoped key in your account settings, hand it to Claude Code, Codex, Cursor or any MCP-compatible client, and it can search jobs, read your resume analysis, track applications and run employer hiring workflows through a documented interface, not a scraped browser session.
Model Context Protocol server
A first-party MCP endpoint over Streamable HTTP, speaking the 2026-07-28 revision and the older handshake-based ones. Scoped tools, resources and workflow prompts.
Scoped, revocable keys
Create a key in your DYNIK settings, tick only the permissions the agent needs, and revoke it in one click. Keys that can change data must carry an expiry.
The same boundaries as the app
An agent sees what its account and key scopes permit. Employer tools need an employer account, and high-impact actions require explicit confirmation.
Multi-step workflows
Search the catalogue, read a job, score it against your resume, and track the application, or post a role, screen applicants and move them through stages.
Works from a terminal or CI
Bearer-token auth over plain HTTPS. No browser, no session cookie, no scraping. The endpoint is stateless, so any HTTP client can drive it.
Structured errors
Every failure carries a stable code and an explicit retryable flag, so an agent can tell "fix the argument" from "try again in 30 seconds".
Machine-readable entry points
MCP endpoint
https://api.dynik.com/api/v1/mcp
POST only, Streamable HTTP.
Server discovery
https://api.dynik.com/.well-known/mcp.json
Endpoint, transport, protocol versions and how to authenticate.
Protected resource metadata
https://api.dynik.com/.well-known/oauth-protected-resource
RFC 9728. Lists the scopes this resource understands.
Plain-text overview for agents
https://www.dynik.com/llms.txt
What DYNIK is and what it can do, without the HTML.
Beta command-line client
https://www.dynik.com/downloads/dynik-cli.py
Python 3.11+, JSON output, and no extra packages. Setup and checksum are in the MCP guide.
What is not available yet
We would rather say this plainly than let you discover it halfway through an integration.
- There is no OAuth authorization server. Create a scoped bearer key in your settings and configure it in a client that supports custom HTTP authorization headers. OAuth-only clients cannot connect yet.
- There is no published SDK. The beta CLI and MCP server use scoped agent keys; existing REST endpoints use the web application’s user authentication.
- There are no outbound webhooks for agent-triggered events yet, so a workflow that needs to react to a change has to poll.