HrFlow.ai is on a mission to solve unemployment, one API at a time.
We know that HR needs vary significantly from one context to another, and this is why we've made sure to segment our products and provide various packages to accommodate every need.
Here's a recap table of the different products and services available:
Profile API
AI Layer | Subscription | Packages | Unit Price (€) |
Parsing | - Monthly - Annual | - < 10k - From 1k to 1M | - From 0.5 to 0.05 - From 0.16 to 0.02 |
Revealing | - Monthly - Annual | - From 1k to 100k - From 10k to 1M | |
Embedding | - Monthly - Annual | - From 10k to 1M - From 10k to 1M | |
Searching | - Annual | - From 10k to 1M | |
Scoring | - Annual | - From 10k to 1M | |
Reasoning | - Annual | - From 10k to 1M |
Job API
AI Layer | Subscription | Packages | Price |
Parsing | - Monthly - Annual | - From 100 to 10k - From 1k to 100k | |
Revealing | - Monthly - Annual | - From 100 to 10k - From 1k to 100k | |
Searching | - Monthly - Annual | - From 100 to 10k - From 1k to 100k | |
Scoring | - Annual | - From 1k to 100k | |
Reasoning | - Annual | - From 1k to 100k | |
Embedding | - Annual | - From 1k to 100k |
Custom Development
In addition to our APIs, we do have a complete team of Designers, Developers, Project Managers, and Data Scientists with extensive experience working on HR solutions for various clients - So trust that your HR project will be in safe hands.
The difference between request-based and record-based pricing
What is a record ?
A record, simply put, is an item or object whose content can be searched or scored. In HrFlow, a record can either be a profile (in a Source) or a job (in a Board).
Therefore, the total number of records equals the sum of the records you have in all your Sources or Boards.
What is a request ?
Within the context of using Hrflow, a request is simply the action of calling an HrFlow service (API) with an item to be processed.
A request can result in a Success or Failure response.
We can distinguish two different types of pricing among the HrFlow services:
Request-based pricing: The cost of total usage is determined based on the number of successful requests made by the user.
For instance, HrFlow Parsing API is priced based on requests.
Record-based pricing: The cost of total usage is determined based on the number of active records in the customer database.
Active records are records that have not been archived or deleted.
HrFlow Scoring is priced based on active records.
Profile Parsing API Usage
You can track your profile parsing consumption by going to your hrflow.ai portal and then to Settings > Usage > Profiles.
Select all of the Sources that have been used to parse profiles in the "choose sources" tab, and then set the period you want to track to get the overall usage.
You may also want to track which sources are used the most by selecting them in the "choose sources" tab, or over which period you have been using Parsing API the most.
As always, feel free to contact us if you have any questions or need help with anything, via chat or email (contact@riminder.net).