Build it
What do you want Affinda and PayCrunch to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Affinda and PayCrunch
Triggers and actions 1 trigger ยท 11 actions
Trigger
Document parsed (instant)Fires via a resthook subscription when Affinda finishes parsing a document.
- Add document
Upload a document (resume, invoice, job description, etc.) to Affinda for parsing.
- Delete document
Delete a document from Affinda.
- Find job descriptions by search expression
Search through parsed job descriptions matching given criteria.
- Get document
Retrieve a specific document and its parsed data by identifier.
- List documents
List all documents uploaded to Affinda.
- Search resumes
Search through parsed resumes matching given criteria.
Action
Get jobGet full wage and detail data for one occupation by its slug. Endpoint: GET /jobs/{slug}.json
- Get SOC code wage data
Get the state-by-state wage table for one Standard Occupational Classification (SOC) code. Endpoint: GET /soc/{code}.json
- List best-paying states by occupation
List the best-paying state for each occupation. Endpoint: GET /states.json
- List jobs
List every occupation covered by PayCrunch, with summary wage data. Endpoint: GET /jobs.json
- List state wages
List wage figures by state for every occupation. Endpoint: GET /state-wages.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.