Tier-5 (API) buyer, reviewing the API and support experience with dates, so you can judge for yourself.

The enrichment itself works: the waterfall found verified emails and we only paid for hits. Five tacos for that alone. The rest is why this review isn't five.

The API design has a trap. v1's POST /enrich/bulk writes every result into one system list ("Extension Leads") with no destination parameter. That list is capped at 500, delete-protected, and when it fills, every enrichment call returns 403 lead_cap_reached. Your pipeline just stops. The portal can't clear it: "Delete leads" errors on that list (we tested with 500 rows and with 2), and there's no move-to-list, only copy.

The support timeline, from the ticket:
- Jul 28: reported the blocked pipeline with full detail. The AI bot's answer recommended a "move to another list" feature that does not exist in the product.
- Jul 28: asked for a human. Got "the team will be back in 2 hours."
- Jul 30: a support rep said he was raising it with the CTO.
- Aug 4: nothing. Asked again.
- Aug 8: told we were "using the wrong endpoint" and should use the new v2 API.
- Aug 9: we tested v2 with a real contact and replied the same day: v2 lets you pick the destination list, but its status endpoint returns no per-contact results at all ("result": null, no linkedin_url, no provider), so there is no way to verify who was actually found. We offered a workflow_id to reproduce. The CTO joined and said "I'm looking into this."
- Aug 13: silence. Asked again.
- Aug 18: gave a final date of Aug 21 before posting this review.
- Aug 25: still nothing. Total: four weeks, zero fixes delivered by support.

We unblocked ourselves: v2's list endpoints let us drain the full list with our own API key, which support apparently didn't know when telling us it was impossible. That's also the fix for anyone else hitting the 403: DELETE /api/v2/lead-lists/{id}/leads works on "Extension Leads."

What's still broken today: safe enrichment (v1, the only version that returns per-contact results) is still hard-wired into a capped list, so the jam will recur for every API customer at 500 contacts.

I'll update this review the day either fix lands: per-contact results on the v2 status endpoint, or a lifted cap on the v1 list. Both are small. The ticket has everything needed to reproduce.