What teams use BuildAPI for
Keys that only work where you say, checked on every call, with the record to prove it. Here is how that fits different kinds of product.
Start BuildingFor Marketplaces
Issue a key per storefront, locked to its own domain, with its use counted separately and its own per-minute limit if you want one.
Learn moreFor SaaS Platforms
Give each customer a scoped key, and suspend, revoke or rotate it without a deploy. Rotation keeps the old value working for a grace window.
Learn moreFor Fintech Teams
Signed, nonce-bound verification you can prove came from us, and a log of every call with the reason for each refusal.
Learn moreFor Agencies
Ship client sites whose keys keep working on the client's domain and stop working if the site is copied elsewhere.
Learn moreFor Security Teams
Scan the DNS, email and web setup of domains you own, watch them for regressions, and push findings to your SIEM or issue tracker.
Learn moreFor Publishers
Serve copy, settings and markup from us at runtime, so a copied site comes up empty instead of showing your content.
Learn moreNot sure you need more than an API key?
See what a plain key leaves out, row by row, including when a plain key is enough.
Compare