TERMS OF SERVICE
Terms.
Effective October 29, 2026 (version 2026-10-29). Last updated October 15, 2026: sections 6, 7 and 9.
These terms take effect October 29, 2026. Until then, the current terms (version 2026-10-08) apply. This version changes three things:
- Section 6: our public dataset on Hugging Face has its own licence, described on the data licence page.
- Section 7: do not send bulk unsolicited messages, do not contact people named in postings except about the job they are named for, and do not combine their details with other data to identify, track or build profiles of them.
- Section 9: do not use the data to discriminate unlawfully against anyone, including in decisions about hiring, pay, credit, housing or insurance.
- 01 · What the service is
- 02 · Accounts and API keys
- 03 · Free allowance, requests and prices
- 04 · Prepaid usage and pay as you go
- 05 · Payment and cancellation
- 06 · What you may do with the data
- 07 · Job postings belong to their publishers
- 08 · What we own
- 09 · Acceptable use
- 10 · Accuracy and availability
- 11 · Suspension and ending the service
- 12 · Disclaimers and limits on our liability
- 13 · Changes to these terms
- 14 · Disputes
- 15 · General
- 16 · Contact
1. What the service is
Headcount Labs collects open job postings from company career sites and job boards, merges postings of the same opening into one job, and makes the jobs available through a REST API and an MCP server that AI agents can connect to (together, the “service”).
These terms are the agreement between you and Headcount Labs for the service. By creating an account, making an API key, or calling the service, you agree to them. If you accept them for a company, you confirm you can bind that company, and “you” means the company. If you accept them as an individual, you confirm you are at least 18.
2. Accounts and API keys
You need an account and an API key or a signed-in MCP connection to use the service. Keep your keys secret. Anything done with your keys or your connection counts as done by you until you revoke the key or tell us at support@headcountlabs.com.
Requests and charges made through a leaked or stolen key, or through mistakes in your own integration (such as repeated identical calls or polling more often than you need), count against your account and are not refunded.
One free allowance per person or company. Do not open extra accounts to get more free jobs.
3. Free allowance, requests and prices
Every API key gets up to 1,000,000 jobs a day free. That is 10,000 requests a day of up to 100 jobs each, shared by every request type, and it comes back each day. Getting one job is free and does not use the allowance.
Past the free allowance you pay per request. A filtered list or a count of filtered jobs costs $0.02 per 1,000 requests. A keyword search or a count of jobs in a keyword search costs $0.20 per 1,000 requests. A request that returns a list brings back up to 100 jobs, and you are charged once per request however many jobs it returns. The current prices are on the pricing page.
Prices drop automatically with the paid requests you make in a calendar month. Your first 1,000,000 paid requests are at full price, the next 9,000,000 are 25% off, and everything past 10,000,000 is 50% off. Each lower price applies only to the requests inside its step, and the count starts again on the 1st of each month.
Every REST API call that lists, searches or counts jobs is one request, however many jobs it returns. Each MCP tool call that searches or counts jobs (search_jobs and count_jobs) is one request, however many jobs or pages it returns, including a search delivered as a file. get_job is free. MCP tools that only read your usage, change your settings, list fields, search the docs or open a delivered file are free.
When your free allowance for the day is used up and you have no prepaid usage and have not turned on pay as you go, calls are refused with a rate-limit error until the free allowance comes back the next day.
4. Prepaid usage and pay as you go
You can add prepaid usage to your account in any amount from $1. It is spent only after your free allowance for the day is used up, at the prices in section 3. Prepaid usage expires 12 months after your most recent purchase.
Instead of prepaying, you can turn on pay as you go in your account. It is off unless you turn it on yourself, and it needs a card on file. Usage past your free allowance and any prepaid usage is then charged to your card on the 1st of the month for the month before. You can turn pay as you go off at any time; the change applies to calls after it.
You are responsible for charges caused by your keys and by agents you connect, including agents acting on their own.
5. Payment and cancellation
Prices are in US dollars and exclude taxes, which we add where the law requires. Payment is handled by Stripe; we do not see or store your card number.
There are no plans, subscriptions or renewals. Prepaid usage is charged when you buy it. Pay as you go is charged in arrears. You can turn off pay as you go at any time from your account, and you then owe only for usage you already had.
Payments are not refunded for unused prepaid usage, except where the law requires it. If we charge you by mistake, tell us within 60 days and we will correct it.
If a payment fails, we may turn off pay as you go and refuse calls past your free allowance until it is paid.
6. What you may do with the data
While your account is in good standing, you may use the jobs you receive in your own products and services, including showing them to your users, analysing them, building search, matching, research and analytics on them, and training or evaluating machine-learning models.
You may not resell, sublicense or redistribute the jobs in bulk as a dataset, feed or API, or use them to build a product that competes with Headcount Labs as a source of job data. Showing jobs to your users inside your own product is not redistribution.
Our public dataset on Hugging Face has its own licence, described on the data licence page. This section covers data you receive through your account.
7. Job postings belong to their publishers
Each job comes from a posting an employer or job board published. We do not own the employers’ text, names or logos, and these terms do not give you rights in them beyond what the law allows. Every job carries a link to its original posting.
Follow any request from an employer or source to correct or remove its posting, and use the data in line with the laws that apply to you, including privacy and anti-discrimination laws.
Do not use the data to send bulk unsolicited email or messages. Do not contact people named in postings except about the job they are named for, and do not combine their details with other data to identify, track or build profiles of them.
Job postings sometimes include personal details such as a recruiter’s name or email. If you process those, you decide how and why, and you are responsible for complying with the privacy and data-protection laws that apply to you.
8. What we own
We own the service and the work we add to the postings: the merging of duplicate postings into jobs, job IDs, normalised fields such as locations, pay and work arrangement, the structure of the data, and the API and MCP tools. Using the service gives you only the rights set out in these terms.
9. Acceptable use
You agree not to: get around usage limits, rate limits or authentication; share keys outside your organisation; reverse engineer the service; run security scans or penetration tests without our written permission; send malware; reach the service other than through the documented API and MCP tools; try to reach other customers’ data; call the service in a way that degrades it for others; use the data to discriminate unlawfully against anyone, including in decisions about hiring, pay, credit, housing or insurance; or use the service for anything unlawful.
We may slow down or refuse calls that put the service at risk. We will tell you if this affects your account for more than a short time.
10. Accuracy and availability
Job data comes from third-party postings and changes constantly. Postings close, move and contain errors, and our merging of duplicates is not perfect. We work to keep the data accurate and current, but we do not promise that any job is complete, correct, still open, or free of duplicates.
We aim to keep the service available but do not promise uninterrupted service. We may change the API and MCP tools; for changes that break existing calls we will give at least 30 days’ notice by email and in the changelog, unless the change is needed for security or legal reasons.
11. Suspension and ending the service
You can close your account at any time. We may suspend or close an account that breaks these terms, does not pay, or puts the service or other customers at risk. Where we can, we will tell you first and give you a chance to fix it.
12. Disclaimers and limits on our liability
The service and the data are provided “as is”. To the extent the law allows, we disclaim all warranties not stated in these terms, including fitness for a particular purpose and non-infringement.
To the extent the law allows, neither of us is liable to the other for lost profits, lost revenue, lost data or indirect, special or consequential damages. Our total liability for any claim about the service is limited to the amounts you paid us in the 12 months before the claim.
You will cover us against claims from third parties, and the reasonable costs of defending them, that arise from your use of the data in breach of these terms or the law.
Neither of us is responsible for delays or failures caused by events outside our reasonable control, such as outages at hosting or network providers, natural disasters, or actions by governments.
Nothing in these terms limits liability that cannot be limited by law.
13. Changes to these terms
We may update these terms. For changes that matter to you, we will email you at least 14 days before they take effect. If you keep using the service after that, the new terms apply. If you do not agree, you can cancel before they take effect.
14. Disputes
Before starting any formal dispute, write to us at support@headcountlabs.com and give us 30 days to resolve it.
15. General
These terms, with our privacy information and any plan terms we agree with you in writing, are the whole agreement between us about the service. If a court finds part of them unenforceable, the rest still applies. If we do not enforce a term straight away, we can still enforce it later.
You may not transfer these terms to someone else without our written consent. We may transfer them to a company that takes over the service, and will tell you if we do.
Notices to you go to the email address on your account; keep it current. Notices to us go to support@headcountlabs.com. Sections about payment owed, data you received, what we own, liability and disputes continue after your account ends.
16. Contact
Questions about these terms, billing or your account: support@headcountlabs.com.