<aside> 👋

The current state is the same as most other platform with API keys, it's up to the dev to protect their keys.

</aside>

Context

Most platforms don't provide any anti abuse measures for client side API keys and just leave it to the dev to handle protecting their key, but Aptos Build aims to reduce the amount of infra our devs need to run and make their integrations as easy as possible. To that end, we should consider enhancing our client side key protections further.

Ideas

The query allowlist is probably the most effective option, abusers will be dissuaded from using a key if it only works for certain queries.

We should give the dev the option to turn on / off detailed error messages when a request is rejected. If they turn off the detailed error messages, it'll be harder for abusers to figure out why they were blocked.