Reference

API and contract changelog

Route, limit, and usage-policy changes that affect public integrations.

2026-10-16 your account is what the rate limit counts, not your address

A fix, in your favour for every paying account, and nothing you have built needs to move. The 120 per client address announced on 2026-10-09 is withdrawn for authenticated requests and replaced by an account limit, because an address is not what identifies a customer.

Area
Rate limits
Change
Authenticated requests are no longer limited by client address. If you call from a shared egress address, a corporate NAT, or a provider that forwards our API, your calls are no longer counted together with everyone else behind it
Area
Rate limits
Change
Your account now has its own limit, shared by every key on it: 600 requests a minute once you have bought API Credits. A key sold more than that delivers it; before this change it could not
Area
Rate limits
Change
Accounts that have never bought API Credits are limited by client address at 120 a minute, which is what the withdrawn limit was. Buying API Credits lifts it
Area
Responses
Change
A 429 names the limit you reached in data.limit_subject, and carries RateLimit-Limit and RateLimit-Policy with RateLimit-Remaining and RateLimit-Reset. Answered requests carry the first two, so your limit is readable off any response. Retry-After is unchanged
Area
Key status
Change
GET /auth/key/status reports account_rpm_limit beside rpm_limit, so the endpoint a 429 points you at can answer which of the two refused you
Area
Rate limits
Change
Repeated failed authentications from one address are now refused with 429. A working integration is unaffected: only a failed authentication counts against it

2026-10-15 an MCP tool call counts once against your limit

A fix, in your favour, and nothing you have built needs to move.

Area
Rate limits
Change
A tool call over MCP was counted twice against the 60 per minute on your key, because the server runs a tool by calling its own REST route. It now counts once, so an MCP client gets the same 60 calls a minute a REST client has always had
Area
Rate limits
Change
The 120 per client address no longer counts MCP tool calls at all. That limit is about one caller's address, and the server's call to itself is not one. The limit itself was withdrawn for authenticated requests on 2026-10-16

2026-10-09 sign in from an MCP client

Additive only: a pasted API key works exactly as it did, and nothing you have built needs to move.

Area
Connecting
Change
An MCP client that supports signing in can connect without a key. It reads where to sign in from the server's own reply, you approve the connection in your browser, and no key is created or pasted. Setup is at mcp
Area
What it can do
Change
Searching and reading people, job and company data is what connecting means. Unlocking contact details is separate: the app has to ask for it and you have to agree, on the same screen
Area
Spending
Change
A connection draws on the same API Credit balance as a key, at the same per-minute limit. The approval screen takes a cap for that one app
Area
Managing it
Change
Connected apps are listed with your keys and can be disconnected there. A connection does not use up the number of API keys you can hold
Area
REST
Change
Unchanged. REST routes take an API key; a connection is for the MCP server

2026-09-24 MCP tool titles, rate limits and enterprise

Additive only: no route, tool name, argument or response field changed, so nothing you have built needs to move.

Area
MCP
Change
Every public tool now carries a title and the annotations readOnlyHint true and openWorldHint false. Clients that list tools show a readable name, and those that honour the hints treat the tools as read-only. A read-only tool still spends API Credits, so give an agent's key a cap
Area
Rate limits
Change
Now written down: 60 requests per minute per API key and 120 per client address, answered past either with HTTP 429 and a Retry-After header in seconds. They were enforced before; only the documentation is new. The address limit was withdrawn for authenticated requests on 2026-10-16
Area
Pricing
Change
The pricing page states the $10 smallest purchase, prices three common tasks, says who can buy contact data (an account that has paid, a plan or a top-up), and adds an enterprise option through [email protected]
Area
Naming
Change
Public documentation calls the unit API Credits, the Platform's name for it; Mira Credits on metix.ai are a different unit. Response fields such as charged_credits keep their names
Area
Agents
Change
Setup pages for Claude, Codex and the OpenAI API, Grok and Muse are at platform.metix.ai/integrations, each checked against the live API

2026-09-20 contact unlock is open

Contact stopped being an announcement. POST /v1/contact/unlock returns a personal email, a work email or a phone number for people you already found, and POST /v1/contact/probe says whether a value exists before you spend on it. Both are in GET /contract, so the request shapes, the caps and the rates are integratable rather than described. See contact.

Area
Pricing
Change
Per value returned, identical on every plan: 8 API Credits for a personal email, 3 for a work email, 15 for a phone number, and 1 per 25 people a probe answers. A kind that comes back not found, pending or disabled is not charged
Area
Repeat requests
Change
An account pays once per person, per kind, per 30 days. A repeat inside that window returns the value with charged_credits 0 and charge_note already_unlocked, so a retry after a timeout does not pay twice
Area
Who can call it
Change
An account that has paid: an active plan, or API Credits bought as a top-up. Signup API Credits are not enough. Probe is open to any account holding API Credits
Area
Phone
Change
Sold on the same rule as the two emails: any account that has paid can buy it. There is no separate per-account grant

2026-09-15 field names and record shape

Every query field and every detail record path has a new name, on the same routes. A query field name is now the path a record returns the value under, so experience.company.name is both the filter and the place to read the employer. Records have a new shape, and _source takes the new paths. The rename tables in the next section list every old name.

Area
Query fields
Change
Names published before 2026-09-15 still run with their old meaning, so a stored query keeps working. They are no longer listed in GET /contract or on these pages, so write new queries with the new names
Area
Withdrawn query fields
Change
regions on people and jobs, and hq_regions on companies, had no new name and were withdrawn instead of kept. A query naming one is refused with unsupported_query_field, and msg says the field has no replacement
Area
_source
Change
Takes record paths. An old name is refused with renamed_source_field, and msg names the path that replaced it. Naming an object or a list, such as experience.company, returns every field under it, on-request fields included. false returns the id alone
Area
Record shape
Change
Every requested field is present: null for an unknown value and [] for an empty list. location, experience[].company, education[].school, headquarters, salary and a job's company are always objects. Booleans are true or false on every dataset, and results follow the order of the requested IDs
Area
Company IDs
Change
experience.company.id on a profile and company.id on a job replace experience.company_id and company_id. Send either to POST /entity/v1/companies/detail-by-id
Area
Ordered filters
Change
education.degree, languages.proficiency, experience.company.size and a company's size take gte, gt, lte and lt as well as eq, in and exists, and compare positions in the published list
Area
Values
Change
education.degree publishes Bachelor, Master and Doctorate. A qualification below a bachelor's, or with degree text that was not recognised, is null in a record, and a filter on Associate or below matches both. languages.proficiency publishes elementary, limited_working, professional_working, full_professional and native, and filters still accept the LinkedIn labels. Company size bands drop the unit: 51-200, not 51-200 employees
Area
Accomplishments
Change
awards, certifications, courses, publications, patents, projects and organizations are lists of entries with their own fields, such as title, issuer and date. Where structured data is not available yet, an entry carries the whole line in title (name for projects and organizations) and its other fields are null. As query fields, awards, certifications, courses, publications and patents match any text of an entry
Area
No longer returned
Change
Fields such as middle_name, connections_count, followers_count, the country codes and regions, every order_in_profile, and a job's posted_raw and salary.string. The rename tables mark each one
Area
Contract
Change
querySpecByEntity.<dataset> adds closedValues, orderedFields, defaultFields, recordFields, recordLists, renamedQueryFields and renamedReturnFields. querySpec.fieldOperators adds ordered
Area
Errors
Change
New refusals for an education.degree or company size value outside its list, and for an operator an ordered field does not take. The languages.proficiency refusal lists the new values, and the salary refusal names salary.currency

2026-09-15 rename tables

Old names on the left, current names on the right. GET /contract publishes the same tables under querySpecByEntity.<dataset>.renamedQueryFields and renamedReturnFields.

Query fields on people. An old name still runs with its old meaning; a name with no new name was withdrawn, and a query naming it is refused.

Before 2026-09-15
active_title
Now
current_title
Before 2026-09-15
active_department
Now
current_function
Before 2026-09-15
management_level
Now
current_seniority
Before 2026-09-15
is_working
Now
is_employed
Before 2026-09-15
is_decision_maker
Now
likely_decision_maker
Before 2026-09-15
experience_months
Now
total_experience_months
Before 2026-09-15
city
Now
location.city
Before 2026-09-15
state
Now
location.state
Before 2026-09-15
country
Now
location.country
Before 2026-09-15
country_iso2
Now
location.country
Before 2026-09-15
country_iso3
Now
location.country
Before 2026-09-15
regions
Now
No new name
Before 2026-09-15
title
Now
experience.title
Before 2026-09-15
role
Now
experience.function
Before 2026-09-15
level
Now
experience.seniority
Before 2026-09-15
is_current
Now
experience.is_current
Before 2026-09-15
started_at
Now
experience.start_date
Before 2026-09-15
ended_at
Now
experience.end_date
Before 2026-09-15
duration_months
Now
experience.tenure_months
Before 2026-09-15
company_name
Now
experience.company.name
Before 2026-09-15
company_type
Now
experience.company.type
Before 2026-09-15
industry
Now
experience.company.industry
Before 2026-09-15
company_size_range
Now
experience.company.size
Before 2026-09-15
company_employees_count
Now
experience.company.headcount
Before 2026-09-15
workplace_city
Now
experience.location.city
Before 2026-09-15
workplace_state
Now
experience.location.state
Before 2026-09-15
workplace_country
Now
experience.location.country
Before 2026-09-15
degree_level
Now
education.degree
Before 2026-09-15
institution_name
Now
education.school.name
Before 2026-09-15
institution_ranking
Now
education.school.rank
Before 2026-09-15
major
Now
education.major
Before 2026-09-15
study_start_year
Now
education.start_year
Before 2026-09-15
graduation_year
Now
education.end_year
Before 2026-09-15
is_studying
Now
education.is_studying
Before 2026-09-15
languages
Now
languages.language
Before 2026-09-15
language_proficiency
Now
languages.proficiency

Record paths on people. An old name in _source is refused with renamed_source_field.

Before 2026-09-15
address
Now
location
Before 2026-09-15
address.city
Now
location.city
Before 2026-09-15
address.state
Now
location.state
Before 2026-09-15
address.country
Now
location.country
Before 2026-09-15
address.full
Now
location.display
Before 2026-09-15
address.country_iso2
Now
No longer returned
Before 2026-09-15
address.country_iso3
Now
No longer returned
Before 2026-09-15
address.regions
Now
No longer returned
Before 2026-09-15
country_code
Now
No longer returned
Before 2026-09-15
active_experience_title
Now
current_title
Before 2026-09-15
active_experience_department
Now
current_function
Before 2026-09-15
active_experience_management_level
Now
current_seniority
Before 2026-09-15
is_working
Now
is_employed
Before 2026-09-15
is_decision_maker
Now
likely_decision_maker
Before 2026-09-15
total_experience_duration_months
Now
total_experience_months
Before 2026-09-15
middle_name
Now
No longer returned
Before 2026-09-15
first_name_initial
Now
No longer returned
Before 2026-09-15
middle_name_initial
Now
No longer returned
Before 2026-09-15
last_name_initial
Now
No longer returned
Before 2026-09-15
connections_count
Now
No longer returned
Before 2026-09-15
followers_count
Now
No longer returned
Before 2026-09-15
services
Now
No longer returned
Before 2026-09-15
education_degrees
Now
No longer returned
Before 2026-09-15
last_graduation_date
Now
No longer returned
Before 2026-09-15
github_contributions_count
Now
github_contributions
Before 2026-09-15
github_repos_summary
Now
github_repos
Before 2026-09-15
github_repos_summary.name
Now
github_repos.name
Before 2026-09-15
github_repos_summary.summary
Now
github_repos.description
Before 2026-09-15
github_repos_summary.stars
Now
github_repos.stars
Before 2026-09-15
github_repos_summary.contributions_count
Now
github_repos.contributions
Before 2026-09-15
experience.role
Now
experience.function
Before 2026-09-15
experience.level
Now
experience.seniority
Before 2026-09-15
experience.start_time
Now
experience.start_date
Before 2026-09-15
experience.end_time
Now
experience.end_date
Before 2026-09-15
experience.duration_months
Now
experience.tenure_months
Before 2026-09-15
experience.order_in_profile
Now
No longer returned
Before 2026-09-15
experience.address_city
Now
experience.location.city
Before 2026-09-15
experience.address_state
Now
experience.location.state
Before 2026-09-15
experience.address_country
Now
experience.location.country
Before 2026-09-15
experience.address_full
Now
experience.location.display
Before 2026-09-15
experience.company_id
Now
experience.company.id
Before 2026-09-15
experience.company_name
Now
experience.company.name
Before 2026-09-15
experience.company_type
Now
experience.company.type
Before 2026-09-15
experience.industry
Now
experience.company.industry
Before 2026-09-15
experience.company_size_range
Now
experience.company.size
Before 2026-09-15
experience.company_employees_count
Now
experience.company.headcount
Before 2026-09-15
experience.company_website
Now
experience.company.website
Before 2026-09-15
experience.company_linkedin_url
Now
experience.company.linkedin_url
Before 2026-09-15
experience.company_logo_url
Now
experience.company.logo_url
Before 2026-09-15
experience.company_facebook_url
Now
experience.company.facebook_url
Before 2026-09-15
experience.company_twitter_url
Now
experience.company.twitter_url
Before 2026-09-15
experience.company_categories_and_keywords
Now
experience.company.keywords
Before 2026-09-15
experience.company_is_b2b
Now
experience.company.is_b2b
Before 2026-09-15
education.institution_name
Now
education.school.name
Before 2026-09-15
education.institution_rank
Now
education.school.rank
Before 2026-09-15
education.institution_url
Now
education.school.url
Before 2026-09-15
education.institution_logo_url
Now
education.school.logo_url
Before 2026-09-15
education.institution_country_iso2
Now
education.school.country
Before 2026-09-15
education.institution_country_iso3
Now
No longer returned
Before 2026-09-15
education.institution_regions
Now
No longer returned
Before 2026-09-15
education.degree_level
Now
education.degree
Before 2026-09-15
education.begin_year
Now
education.start_year
Before 2026-09-15
education.is_current
Now
education.is_studying
Before 2026-09-15
education.order_in_profile
Now
No longer returned
Before 2026-09-15
languages.order_in_profile
Now
No longer returned

Query fields on jobs. An old name still runs with its old meaning; a name with no new name was withdrawn, and a query naming it is refused.

Before 2026-09-15
application_active
Now
is_open
Before 2026-09-15
city
Now
location.city
Before 2026-09-15
state
Now
location.state
Before 2026-09-15
country
Now
location.country
Before 2026-09-15
country_iso_2
Now
location.country
Before 2026-09-15
location
Now
location.display
Before 2026-09-15
regions
Now
No new name
Before 2026-09-15
company_name
Now
company.name
Before 2026-09-15
posted
Now
posted_date
Before 2026-09-15
posted_is_estimated
Now
posted_date_is_estimated
Before 2026-09-15
required_months_of_experience
Now
min_experience_months
Before 2026-09-15
salary_currency
Now
salary.currency
Before 2026-09-15
salary_min
Now
salary.annual_min
Before 2026-09-15
salary_max
Now
salary.annual_max
Before 2026-09-15
salary_unit
Now
salary.period

Record paths on jobs. An old name in _source is refused with renamed_source_field.

Before 2026-09-15
external_url
Now
apply_url
Before 2026-09-15
application_active
Now
is_open
Before 2026-09-15
required_months_of_experience
Now
min_experience_months
Before 2026-09-15
posted
Now
posted_date
Before 2026-09-15
posted_is_estimated
Now
posted_date_is_estimated
Before 2026-09-15
posted_raw
Now
No longer returned
Before 2026-09-15
posted_reference_date
Now
No longer returned
Before 2026-09-15
applicants_count_raw
Now
No longer returned
Before 2026-09-15
company_name
Now
company.name
Before 2026-09-15
company_id
Now
company.id
Before 2026-09-15
company.url
Now
company.linkedin_url
Before 2026-09-15
city
Now
location.city
Before 2026-09-15
state
Now
location.state
Before 2026-09-15
country
Now
location.country
Before 2026-09-15
country_iso_2
Now
No longer returned
Before 2026-09-15
regions
Now
No longer returned
Before 2026-09-15
regions.region
Now
No longer returned
Before 2026-09-15
salary.min_value
Now
salary.min
Before 2026-09-15
salary.max_value
Now
salary.max
Before 2026-09-15
salary.unit
Now
salary.period
Before 2026-09-15
salary.string
Now
No longer returned

Query fields on companies. An old name still runs with its old meaning; a name with no new name was withdrawn, and a query naming it is refused.

Before 2026-09-15
categories_and_keywords
Now
keywords
Before 2026-09-15
size_range
Now
size
Before 2026-09-15
employees_count
Now
headcount
Before 2026-09-15
employees_count_change_yearly_percentage
Now
headcount_growth_yoy_pct
Before 2026-09-15
followers_count
Now
linkedin_followers
Before 2026-09-15
hq_city
Now
headquarters.city
Before 2026-09-15
hq_state
Now
headquarters.state
Before 2026-09-15
hq_country
Now
headquarters.country
Before 2026-09-15
hq_country_iso2
Now
headquarters.country
Before 2026-09-15
hq_full_address
Now
headquarters.address
Before 2026-09-15
hq_regions
Now
No new name
Before 2026-09-15
last_funding_round_amount_raised
Now
last_funding.amount
Before 2026-09-15
last_funding_round_date
Now
last_funding.date
Before 2026-09-15
stock_exchange
Now
stock_listings.exchange
Before 2026-09-15
stock_ticker
Now
stock_listings.ticker
Before 2026-09-15
last_updated_at
Now
updated_at

Record paths on companies. An old name in _source is refused with renamed_source_field.

Before 2026-09-15
categories_and_keywords
Now
keywords
Before 2026-09-15
size_range
Now
size
Before 2026-09-15
employees_count
Now
headcount
Before 2026-09-15
employees_count_change_yearly_percentage
Now
headcount_growth_yoy_pct
Before 2026-09-15
followers_count
Now
linkedin_followers
Before 2026-09-15
hq_city
Now
headquarters.city
Before 2026-09-15
hq_state
Now
headquarters.state
Before 2026-09-15
hq_country
Now
headquarters.country
Before 2026-09-15
hq_full_address
Now
headquarters.address
Before 2026-09-15
hq_street
Now
headquarters.street
Before 2026-09-15
hq_zipcode
Now
headquarters.postal_code
Before 2026-09-15
hq_country_iso2
Now
No longer returned
Before 2026-09-15
hq_country_iso3
Now
No longer returned
Before 2026-09-15
hq_regions
Now
No longer returned
Before 2026-09-15
last_funding_round_date
Now
last_funding.date
Before 2026-09-15
last_funding_round_amount_raised
Now
last_funding.amount
Before 2026-09-15
stock_ticker
Now
stock_listings
Before 2026-09-15
stock_ticker.exchange
Now
stock_listings.exchange
Before 2026-09-15
stock_ticker.ticker
Now
stock_listings.ticker
Before 2026-09-15
last_updated_at
Now
updated_at

2026-09-11 operators per field, error codes, cursors, and docs

Each field takes the operators its kind supports, and GET /contract lists them for every field. match on a field compared whole is refused instead of quietly matching nothing. Every error response carries an error_code, with new codes for invalid IDs, invalid cursors, and requests that are not query refusals. A cursor issued before this release is refused; start that search again from the first page.

Area
Operators
Change
Free-text fields take match, eq, in and exists. Fields compared whole (categories, names, codes, yes or no) take eq, in and exists, and match on them is refused with the operators that work. Numbers and dates take eq, in, gte, gt, lte, lt and exists
Area
Contract
Change
querySpecByEntity.<dataset>.fieldOperators lists the operators for every field. querySpec.fieldOperators is keyed text, exact, numeric and date; the nonNumeric key is gone
Area
Errors
Change
A 400 outside the query tree carries invalid_request rather than query_spec. A detail ID this API did not issue returns invalid_id, and msg names its position. A bad after returns invalid_cursor. 403, 404, 405 and 503 responses carry forbidden, not_found, method_not_allowed and service_unavailable
Area
Paging
Change
The next cursor is sealed and no longer carries an internal id. A cursor issued before this release is refused with invalid_cursor
Area
MCP
Change
metix_get_profiles, metix_get_jobs and metix_get_companies accept _source as a list of field names, as the REST routes do. The server identifies itself as Metix AI API
Area
Search size
Change
Every key may ask for up to 10,000 IDs per page. Omitting size returns 100
Area
Values
Change
The people page lists the values of role and company_type, and active_department gains General Management
Area
Salary
Change
salary_currency in an all nested inside the same all now scopes salary_min and salary_max, the same as when it sits in that all directly. A currency inside any or not still does not
Area
Docs
Change
Each section heading in a .md page has an anchor with the section id, so a docs_url fragment such as #query-refusals lands on its section. GET /docs lists nav_label for each page, and the catalog and each page carry schema_version

2026-09-08 applicants, dates, salary, and created_at

Numeric and date fields now accept gt and lt, and also eq and in. Job created_at is no longer queryable or returned on the public surface. Job salary search now compares same-currency annual pay.

Area
Applicants
Change
Write any eq, in, or range. The API maps it onto (0, 24], [25, 200], and (200, +inf). lte 24 and lt 25 are the first-25 bucket; gte 201 and gt 200 are the over-200 bucket
Area
Operators
Change
gte, gt, lte, lt, eq, in, and exists on numeric and date fields. match on those fields is still refused
Area
Jobs
Change
created_at is removed from public query and return. Use posted for recency. updated_at stays
Area
Salary
Change
salary_min and salary_max are same-currency annual pay. A comparison needs salary_currency in the same all. salary_unit is hour, day, week, month, or year and is optional. The response still returns the posting's own salary object
Area
Errors
Change
docs_url lands on the matching docs page. The errors page catalogs every public error_code and the Query Spec refusals

2026-09-07 query fields and errors

Job and company range fields that previously refused a filter now answer. Failures also carry a stable error_code and a docs_url that points at the matching docs page.

Area
Jobs
Change
salary_min, salary_max, applicants_count, and posted accept gte and lte. salary_unit and posted_is_estimated are new query fields
Area
Salary
Change
A range is only comparable inside one salary_currency and one salary_unit. Units are not normalized
Area
Applicants
Change
25 to 200 are exact. lte 24 is the first-25 bucket. gte 201 is the over-200 bucket
Area
Posted
Change
A calendar day, currently estimated from the source wording. created_at remains ingest time
Area
Companies
Change
founded_year accepts gte and lte as a four-digit year
Area
Errors
Change
The envelope adds error_code and docs_url. An empty all points at GET /contract
Area
Crawlers
Change
GET /robots.txt answers 200 and disallows every path

2026-08-20 public surface

The public API is now three datasets and nothing else: people, jobs, and companies. Each is searched with a Query Spec tree and read through its own detail route, and the system routes report version and key status. Everything documented today is on the api page.

Area
Datasets
Change
People, jobs, and companies. Anything outside those three is withdrawn and undocumented
Area
Structured search
Change
The Query Spec tree replaced the earlier flat filter parameters on every dataset
Area
Paging
Change
Search responses carry a next cursor; pass it back as after
Area
Detail batches
Change
Entity detail accepts up to 100 IDs per request
Area
Search window
Change
Search returns up to 1000 IDs per page
Area
Contact enrichment
Change
Announced, not open. No endpoint, request shape, or price is published
Area
Skills
Change
Four published skills, one per dataset plus a coordinator

Withdrawn routes

A route that is not documented on the API reference is not part of the public surface. Withdrawn routes are not listed here by name and have no replacement mapping: rewrite the call against the dataset page you need.

Query Spec is the structured interface

One grammar covers all three datasets, so what changes between them is the field list rather than the request shape. The full grammar, including composition, operators, relative dates, same-record scopes, and cursor paging, is on the query spec page.

  • Composers all, any, and not compose leaves into a boolean tree.
  • Operators are eq, in, match, gte, lte, gt, lt, and exists, one per leaf.
  • Date fields accept relative values such as now-30d, resolved server-side.
  • People carry same-record scopes; jobs and companies are one document each and carry none.
  • A refused query is translated before it is charged, so it costs nothing.

Usage contract

  • Query Spec search on any dataset settles by returned ID count: ceil(returned IDs / 25).
  • Natural-language people search adds a 5 API Credit base to that.
  • Profile, job, and company detail settle by found record count: ceil(found records / 5).
  • Paging spends per page, so 1000 IDs cost the same in one page as in four.
  • API Credit balances use additive active buckets with nearest-expiry-first spend order.

Integration checklist

  • Treat every search response as IDs, and fetch records through the detail route.
  • Keep one operator per leaf, and split a bounded range into two leaves.
  • Keep detail batches at 100 IDs or fewer.
  • Stop paging when next is absent rather than when a page comes back short.
  • Do not treat browser billing redirects as an API Credit grant.