Idynic meets you where the roles turn up
A role turns up in a browser tab, in your inbox, or as a link someone sends you. Idynic takes it from any of those and scores it against the same portrait. Once it is in, that portrait is reachable from the tools you already work in.
Three ways in, one result
Whichever route a posting takes, it comes out the same end: an opportunity scored against the evidence already in your portrait.
Paste it
You have
A job link, or the description text you copied
- Drop it into Idynic
- It fetches the posting and pulls out the requirements
You get
Scored against your portrait, with the evidence behind the score
Works for any posting you can reach by URL or copy by hand.
Forward it
You have
A job alert from LinkedIn, Indeed, or a recruiter
- Forward the email to your own intake address
- Idynic reads the roles out of the message
You get
Waiting in your review inbox, yours to keep or discard
Turn it on in Settings and you get an address of your own at intake.idynic.com. Regenerate it whenever you like: the old one stops working the moment you do.
Save it as you browse
You have
A posting open in a tab
- Click Save in the extension
- The work queues, so you can close the popup and keep reading
You get
Saved, researched, matched, and tailored by the time you look
The extension tells you before you click if the role is already in your list.
Live now: connect it to your own tools
Your portrait is not stuck inside this website. Three surfaces are running today, and all three answer to credentials you issue and can revoke.
MCP server
Point Claude, Cursor, or any MCP client at Idynic and it can read your portrait and act on it: add a role, tailor an application, draft a cover letter, pull a share link. Connect over the hosted endpoint, or run the published npm package locally.
- Hosted at idynic.com/api/mcp, authenticated with an API key you issue
- Or run @atriumn/idynic-mcp on your own machine
REST API
The same endpoints the app itself calls, under /api/v1. Issue a key from Settings, give it only the scopes it needs, and revoke it when you are done.
- Scoped keys: read and write are separate, per area
- A key with no scopes gets no access
Chrome extension
Save a posting from the page you are reading, and prefill applications on Greenhouse, Workable, and Fillout. It marks every field it touched and every field it deliberately left alone. You press submit.
- Chrome, Edge, Brave, and other Chromium browsers
- At install it can reach idynic.com and nothing else
Not live yet, and what that means
These are on the list and not in your hands. Nothing below is running in your account today, so they are separated out rather than mixed in above with a small label.
GitHub check-ins
Reads your public GitHub activity so a check-in can ask a better question than “what have you been up to?” It is off by default and still behind a flag.
Deliberate limit, whatever the flag says: a digest only grounds the question. Activity never becomes evidence in your portrait, and nothing it reads is stored beyond a short summary.
Slack
The idea is that a project announcement or a round of praise in a channel becomes a story you can approve into your portrait.
No Slack code exists yet. This is a waitlist, not a beta.
LMS & certs
Course completions and certifications arriving as evidence instead of a line you retype from a PDF.
No LMS code exists yet. This is a waitlist, not a beta.
Building against it
The API and the MCP server are the same surface the product uses, so anything the app does with your portrait, your own code can do too. If you are working on something that needs a piece we have not exposed, say so and we will look at it.
Ask for an endpoint