Work across people, jobs, and companies

Start here when the request is a goal rather than one dataset. This skill picks the order of calls and chains them on ids.

Then set it as METIX_KEY. Do not paste the key into the chat or a file.

Who it is for

Agents that have to decide whether the next call is people, jobs, or companies, and what it will cost. A single dataset should use the focused skill instead.

What it does

What you need

This skill plus the three focused skills when the agent needs their field rules. METIX_KEY. HTTPS to https://mira-api.metix.ai. Check GET /auth/key/status before a run that will pull thousands of records. That call is free.

Three measured steps

Run on 2026-10-13 against API 2.1.2. They reuse the focused skills' queries, because this skill does not add an endpoint of its own.

Posting, then the employer by id

Data engineer jobs posted in the last 30 days: total 15433. The posting's company name was Unison Group, posted 2026-10-04. The company record for that posting's company.id is named Unison Consulting, industry IT Services and IT Consulting, size 201-500, headquarters country Singapore.

Count people before reading them

Backend engineers in the United States, five or more years, current financial services: total 591. No profile detail was pulled.

A hiring-demand count with no people call

Software engineer postings in the last 7 days: total 12059. One posting title was "Software Engineer / Senior Software Engineer" at Koniag Government Services, posted 2026-10-08. No people query followed.

Limits

The same credit rules as the focused skills: ceil(results / 25) on search, ceil(found / 5) on detail. Natural-language people search adds a 5 credit base and was not called. Contact unlock was not called. Totals are exact below 100,000.