6,000 requests a minute, and a provider registry that may or may not take your key.
A Reverse Contact API key and an Instantly API v2 key with the right scopes
Contacts, Companies, one way, in.
Instantly is where a bulk enrichment pass stops being a planning exercise. Six thousand requests a minute across the workspace is ten times what Salesloft allows a whole team and a hundred times what Smartlead allows on Standard, so the shape of the build is simply enrich everything and upload. The interesting unknown is the provider registry, which documents a bring-your-own-key model with a cost of zero on the workspace key, and which names no providers publicly. Worth one email to Instantly before building the pipeline the long way.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| The list, before upload | One way, out | Enrich each row from its email with /v2/enrich/persons. 2 credits on a match, free on a check. |
| Lead upload | One way, in | POST the enriched leads into the campaign with their custom variables. |
| Webhook events | One way, out | Typed events fire back out on campaign activity, which is how a reply reaches a CRM. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and your pipeline decides which variables get written. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
Everything happens outside Instantly: enrich the row, then upload it. The limits barely constrain this, so what is worth laying out is which values become which fields and which parts of the response should stop a row being uploaded at all.
| In Instantly | In Reverse Contact | What to know about the match |
|---|---|---|
| An email on the row | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Once per company rather than once per lead at it. |
| A profile URL already on the row | POST /v2/fetch/persons, 1 credit | Half the credits, and unmetered from the $249 plan rather than the $699 one. The cheapest route into this pair if your list was sourced from profiles. |
| currentPosition.title and company.name | Custom fields on the lead | The two values most openers reference. The names have to match the sequence variables, and a near-miss renders the fallback rather than erroring. |
| An API v2 key | Scoped per resource | An endpoint refuses a key lacking the relevant scope, which is the right behaviour and means an all:all key in development hides a production failure. |
| The provider registry | credentialSource and effectiveCostPerAction | Documented as a shape rather than a list: workspace_key, instantly_key or unavailable, with a cost of 0 on a workspace key. Which providers it holds is not published, so treat a bring-your-own-key route as a question rather than a capability. |
| Add leads to a campaign | Batches of 100, two seconds apart | Instantly's own recommendation, and worth following under a generous ceiling because the ceiling is shared across every key in the workspace and with API v1. |
| Anything outbound to Reverse Contact | Only what your pipeline sends | This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. |
This matters more on this page than on any other in the set, for a reason that sounds backwards: nothing in the Instantly limits will slow a mistake down. Six thousand requests a minute means a suppression rule you forgot to write reaches thousands of people before anybody notices.
| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes the email acceptable, and it is the one outbound failure that cannot be apologised for afterwards |
| currentPosition.companyName disagrees with your record | They have changed job, so a campaign written for the old role is about to reach the new one. Re-qualify rather than refresh |
| isOpenToWork | They are looking to leave. A reason for a human to read the opener once, rather than an automatic stop |
| data is null, with a confidence score | Nothing matched confidently. Sending the fallback text is a decision, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from long ago | Stale rather than wrong, which is the one case where a 2-credit live refresh earns its money |
| followersCount and hasVerificationBadge | Not suppression at all. Listed because they are the fields teams reach for as a seniority proxy, and neither is one |
A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six in the response rows and four documented exclusions, each one's note, and the seven vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The suppression table is the whole argument of this page. Every other sender here has a limit low enough that a bad rule produces a trickle of bad emails and somebody spots it; this one will send the lot inside the hour. The check worth writing first is the current employer comparison, because it is two values and three lines.
Instantly publishes 6,000 requests a minute and 100 a second for the whole workspace, shared between API v1 and v2 and across every key. That figure is generous enough to be misleading, because several routes carry their own much tighter limit and the headline one never applies to them. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The call you are making | The 6,000 a minute workspace budget | Safe to call in a tight loop | Safe to run beside another bulk job |
|---|---|---|---|
| Adding leads to a campaign | Yes | Yes | Partly |
| Reading or updating a lead | Yes | Yes | Partly |
| Listing emails | No | No | No |
| A test send | No | No | No |
| The AI reply label test | No | No | No |
Counted off that grid, of fifteen pairings: four give you yes, two give you partly, nine give you no. The bottom three rows are the finding, and the practical reading is that Instantly is extremely fast at the two things this build does and slow at the things you would use to check on it. So verification by polling is the wrong instinct here: read the rendered email on one lead instead, which costs one request and tells you more than a loop over the listing endpoint ever will.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
An email to Instantly
Instantly documents an integration provider registry with credentialSource values of workspace_key, instantly_key and unavailable, and an effectiveCostPerAction of 0 on a workspace key. It does not publish which providers are in it. One email could replace this entire pipeline with a key paste, so it is worth sending before an afternoon is spent.
Your own pipeline
Personalisation renders at send time, so a lead uploaded without the fields a sequence references gets the fallback and nothing later repairs the email that went. Enriching first also lets you drop the rows that did not resolve rather than sending to them.
Instantly: API v2 keys
API v2 keys carry scopes per resource, and an endpoint refuses a key that lacks the right one. A pipeline built and tested with an all:all key can fail on a narrower production key, which is correct behaviour and an easy afternoon to lose. Test on the key you will ship.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a bulk pass spends 2 credits only where it has to. With 6,000 requests a minute available on the Instantly side, Reverse Contact credits are the only budget this build has to respect.
Your pipeline
A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each is a row to drop rather than a row to personalise better. This matters more here than anywhere else in the set, because nothing in the limits will slow you down enough to notice.
Your pipeline
Instantly recommends batches of 100 with a 2-second wait between them, and running automations several times a day rather than once. Worth following under a generous ceiling, because the ceiling is shared across every key in the workspace and with API v1 as well.
Instantly: the per-endpoint limits
Listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. The headline figure does not apply to every route, so check the one you intend to call repeatedly.
Instantly: a campaign with one mailbox
The rendered first email is the only artefact that proves the mapping worked. The API reporting success means the lead was accepted, which is a different claim, and the two are easy to confuse at six thousand requests a minute.
The first step is the only one with real leverage and it is an email rather than a task. Everything else is the same build as the other four senders with the constraints removed, which makes the suppression rule in step five the thing that matters most: the Smartlead version is slow enough that a mistake gets noticed, and this one is not.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/instantly-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/instantly-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyAPI v2 keys carry scopes per resource and an endpoint refuses a key that lacks the right one. A development key with broad scopes hides the problem entirely.
Test on the key you intend to ship. The refusal is correct behaviour rather than a fault, which is why nothing in the logs will suggest a permissions problem until you look for one.
WhyThe limit applies to the entire workspace and is shared between API v1 and v2 even across multiple API keys, so it is not per job and not per key.
Serialise the jobs or accept the halving. Instantly recommends batches of 100 with a 2-second wait and running automations several times a day rather than once.
WhySeveral routes carry their own limit regardless of the headline figure: listing emails is 20 a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace.
Take those out of any loop. No upgrade or pacing on the main budget affects them, because they are not governed by it.
WhyPersonalisation renders at send time from whatever the lead record holds, and a field name that does not match the sequence variable renders the fallback rather than failing.
Send one lead to a campaign with one mailbox and read the rendered email. It is the only place this is visible and it costs one request.
WhyAt 6,000 requests a minute a missing suppression rule has no natural brake. Nothing in the limits slows a bad rule down enough for anybody to notice it first.
Compare currentPosition.companyName against your own value and check isInRemembrance before upload, not after. On this pair that rule is worth more than any personalisation it prevents.
WhyInstantly documents the registry as a shape rather than a list: credentialSource of workspace_key, instantly_key or unavailable, and an effectiveCostPerAction of 0 on a workspace key. The providers themselves are not published.
Ask Instantly directly before building the pipeline the long way. A bring-your-own-key route would replace most of this page, and it is one email rather than an investigation.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the reason the lookup did.
WhyThis is the one pair in the set with no external brake. A reverse lookup is 2 credits, the Instantly side allows 6,000 requests a minute, and nothing in between enforces a pace.
Call the free check first and refresh only what is stale, set a per-key rate limit on the Reverse Contact side, and read quotas.workspace.credits.left on every response rather than at the end of the run.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
teh data ownership thing is brutal. Lost 3 months of enriched contacts when we switched sequencers last year [...] Now we keep everything separate - Prospeo for the contact data, Close for CRM, Instantly just for sending. Export everything weekly just in case
r/SaaS·April 2026·6 points
The clearest statement anywhere in the harvest of why a data layer sits underneath a sender rather than inside one. Instantly just for sending is the division this page assumes, and the reason given is not quality or price but what happens on the day you change the sender. The weekly export is a reasonable response to having been burned once.
From what I've seen, automated enrichment gets you 70-80% there, but the rest is messy: wrong titles, outdated emails, weird company hierarchies. For high-stakes outreach, someone still needs to double-check, especially for small businesses or niche industries.
r/b2b_sales·October 2025·1 points
One person's estimate rather than a measurement, and it happens to bracket the figure Reverse Contact publishes, which is a 70%+ identity match rate measured globally. Treat the agreement as a coincidence worth noticing rather than as corroboration, and measure your own on 500 rows: that is what the published number says to do and it is the only figure that decides this build.
We had Zapier chains gluing Apollo, Clay, HubSpot, and a couple scraping tools together, and every break meant some lead source silently died for a week. The worst part was context switching and debugging, not even the cost. [...] For us, discovery and timing mattered more than fancy reporting, so we were okay with weaker dashboards if it meant fewer moving parts.
r/microsaas·April 2026·1 points
Silently died for a week is the failure mode this whole block keeps returning to, and it is the reason a confident null matters: a pipeline that writes nothing and reports success is indistinguishable from one that is working. The last sentence is the right way to choose between the routes on this page, because fewer moving parts is a feature you can audit.
That's interesting. Out of the 5.1% reply rate, how many actually turn up for a meeting and how many become clients? I'm also curious about the quality of your emails. Do you do any sort of research before you send out an email to a potential client?
r/agency·October 2025·4 points
Asked under a post reporting four months of improvement, and the second question is the one this page can answer. Research before the send is a resolved rate you can count on upload day; a reply rate is the same information four weeks later, with the sending reputation already spent on whatever did not resolve.
I feel like the answer depends on where your biggest bottleneck is. If it's finding prospects, Apollo is still hard to beat. If it's sending and deliverability, Instantly is a solid choice. If you're trying to reduce tool sprawl, an all-in-one platform starts to make more sense.
r/AiAutomations·July 2026·2 points
Three bottlenecks, and this page addresses none of them. That is the point worth making honestly: Reverse Contact is not a prospecting database, not a sender and not a consolidation play. It is the thing that fills the record, which only matters once one of those three is already working.
Nobody discusses this pair by name, so the search was for the job: resolving a cold list before a sender touches it. The best comment in the set is somebody who lost three months of enriched contacts when they changed sequencer and now keeps the data layer separate on purpose, which is this page's argument made by somebody who learned it expensively. The accuracy thread is the other one worth reading, because it lands on the same figure the vendor publishes.
The first quote is the page in three sentences and the second is the reason to run the test before believing any of it. On this pair there is no external brake, because the Instantly side allows 6,000 requests a minute and nothing in between enforces a pace, so the resolved rate you measure on 500 rows is the only thing standing between a credit balance and an afternoon.
Rate limits are usually a footnote and here they change the design. Enriching a 50,000-row list against Smartlead's Standard tier means fifty hours of hourly ceilings to work around; against Instantly it is a few minutes of batched requests. That difference decides whether enrichment is a step in the list build or a scheduled job somebody maintains, and it is the most consequential thing on this page.
The provider registry is the part worth a question rather than an assumption. Instantly documents a model where a data provider's actions cost the workspace nothing when the workspace holds its own key with that provider, which is exactly the arrangement a buyer of two products wants. What the public documentation does not do is name the providers, so this page will not claim Reverse Contact is one. Ask Instantly before you build the pipeline the long way, because the answer changes the work.
Whichever route the answer points at, the ordering is the same as it is on every sequencer page here. Enrich before the upload, drop the rows that returned null rather than sending to them, and measure your own resolved rate instead of anyone's published match rate. The Smartlead page reaches that from the opposite end of the limits, and Salesloft from the opposite end of the market, which is a reasonable sign that it is the right order rather than a convenience.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Instantly, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
A hundred requests a second and 6,000 a minute, shared between API v1 and v2 and across every key in the workspace. That is an order of magnitude more headroom than any other sequencer in this directory, which makes a bulk enrichment pass an ordinary operation rather than something to schedule around.
Their documentation describes an integration provider registry where each data provider has lookup actions, a credit cost per action, and a credentialSource that can be the workspace's own key, in which case the action costs the workspace nothing on Instantly's meter. The public documentation names no providers, so whether Reverse Contact is one is a question for Instantly rather than something their docs answer.
The way it runs for every other sequencer here: enrich the rows before they are uploaded to a campaign, through your own call to /v2/enrich/persons, a Clay table, or the native Zapier app. The limits mean you can do it in bulk without pacing.
Two credits for a reverse lookup from an email when it resolves, and nothing for a freshness check first. Reverse Contact publishes the credit cost per call and no dollar rate behind it, so the money figure depends on the pack or plan the credits came from.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.