# Native bot protection for public Pickaxe tools

**URL:** <https://community.pickaxe.co/t/native-bot-protection-for-public-pickaxe-tools/8807>\
**Category:** Feature Requests\
**Created:** [September 3, 2026, 6:38pm UTC](https://community.pickaxe.co/t/native-bot-protection-for-public-pickaxe-tools/8807 "2026-09-03T18:38:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gotinternetmarketing](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/gotinternetmarketing/32/6587_2.png) [@gotinternetmarketing](https://community.pickaxe.co/u/gotinternetmarketing)\
**Post date:** [September 3, 2026, 6:38pm UTC](https://community.pickaxe.co/t/native-bot-protection-for-public-pickaxe-tools/8807/1 "2026-09-03T18:38:43Z")

</div>

Feature request: Native bot protection for public Pickaxe tools.

Please consider adding CAPTCHA, Cloudflare Turnstile, hCaptcha, or invisible bot protection before a public embedded tool can be submitted.

This would help protect creators from bots or abuse that could run up API or credit costs.

---

<div class="post-metadata">

**Author:** ![danny\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/danny_support/32/3492_2.png) [@danny\_support](https://community.pickaxe.co/u/danny_support)\
**Post date:** [September 16, 2026, 8:44pm UTC](https://community.pickaxe.co/t/native-bot-protection-for-public-pickaxe-tools/8807/2 "2026-09-16T20:44:42Z")

</div>

Hi @gotinternetmarketing ,

For tools where you’re concerned about abuse, you can require visitors to verify their email before using them and set a usage limit for each member.

Under your deployment’s **Access** tab, choose **Require Login** and connect a **Member Access Group**. This gives you control over access and credit consumption without adding a CAPTCHA to each submission.