Build it
What do you want BigML 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 BigML and PayCrunch
Triggers and actions 1 trigger ยท 9 actions
Trigger
New projectTriggered when a new project is created in BigML. Polls the BigML projects list endpoint and emits each project, deduplicated by its resource id.
- Get Resource Status
Retrieve a BigML resource by id (source/dataset/model/prediction) to poll its status and read results.
- List Datasets
List BigML datasets, optionally filtered/paginated (GET /dataset).
- List Models
List BigML models, optionally filtered/paginated (GET /model).
- List Sources
List BigML sources, optionally filtered/paginated (GET /source).
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.