Instatus vs Tomba email finder

Instatus's REST API (`api.instatus.com`) lets a status-page owner script incident and maintenance updates, component status changes, and subscriber management for their own hosted status page. Every request must carry an `Authorization: Bearer <API_KEY>` header and a page ID from the dashboard, confirmed live via a 401 "API key is not sent in request header" response on an unauthenticated GET to `/v1/pages`; the same endpoint echoes a matching `access-control-allow-origin` on both a GET and a separate OPTIONS preflight sent with an Origin header, confirming the API is browser-callable. Instatus itself runs a permanent free-forever plan alongside paid per-project tiers, with no separate gate on API access.

Tomba's Email Finder API discovers and verifies professional email addresses from a company domain or a person's name, and doubles as a B2B prospecting and lead-enrichment tool via linked domain-search and phone-finder endpoints. It authenticates with a paired `X-Tomba-Key`/`X-Tomba-Secret` header set rather than a single token, and a live Origin-header probe confirms it explicitly supports browser CORS, echoing the request Origin with credentials enabled on both a GET and an OPTIONS preflight.