API Keys

ZeroGTM uses several external APIs for the enrichment pipeline: Google Maps (RapidAPI), OpenWeb Ninja, Anymail Finder, and optionally OpenAI or Anthropic. Keys are stored per user or in server env and never logged. You can use your own keys (BYOK); when you do, those steps don’t consume plan credits on hosted tiers.


Which APIs

Service Used for Where to get
RapidAPI (Google Maps) Map scrape — Google Maps scraper lead extraction RapidAPI
OpenWeb Ninja Find emails — lead enrichment (emails, phones, socials) OpenWeb Ninja
Anymail Finder Find DM emails — email finder for decision makers (email finder by name; email finder by phone number where supported) Anymail Finder
OpenAI or Anthropic Optional: casualise names, AI summaries, agent OpenAI / Anthropic

Where to Set Keys

Mobile app (user-level, BYOK)

In the app Settings, you can add API keys per service. Those are stored per user (in api_keys table). When a job runs, the worker (or Edge Function) can use the user’s key for that service so the step is BYOK and doesn’t deduct credits.

Worker / server

For self-hosted or when the platform provides keys, set env vars on the worker (and optionally Edge Functions), e.g.:

Exact names depend on the worker code (see workers/*.py and your .env.example).

Edge Functions

If any Edge Function calls an external API (e.g. OpenAI for casualise-names), set the corresponding env in the Supabase/Edge Runtime config.


BYOK and Billing

See Pricing for credit rules and Self-Hosted for server env setup.

ZeroGTM plugs into email finder and lead enrichment providers via email finder API and lead enrichment tools—using API keys you own (BYOK) or keys supplied by the platform.

Getting started →
Enrichment pipeline →
Self-hosted →
Pricing →
Features → · Compare →