What authentication does the HireArt API use?

The HireArt API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, and each token is scoped to the authenticated employer. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I read worker and assignment data with the HireArt API?

Yes. GET /workers lists the roster and GET /workers/{id} returns one worker, while GET /assignments lists placements and GET /assignments/{id} returns a single assignment. All list endpoints paginate with page and per_page query parameters and report total_count and total_pages in the body.

What are the rate limits for the HireArt API?

The HireArt spec documents a limit of 100 requests per 60 seconds per API key, and the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds until the limit resets. Honour the Retry-After value when backing off.

How do I pull HireArt staffing data through Jentic?

Search Jentic with the query 'list staffing assignments', load the schema for GET /assignments, and execute it, then call GET /workers to resolve the staffed workers. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the HireArt API?

Yes. Write a rule that allows only the list and fetch reads you need, such as GET /assignments and GET /workers/{id}, so the agent can report on staffing and touch nothing else, and every call it makes is logged. Because the whole API is read-only, there are no write or delete operations for the agent to reach.