hammadtq

OpenBotAuth helps publishers control automated access from AI crawlers and agents. It verifies requests using RFC 9421 HTTP Message Signatures (via a configurable verifier) and applies per-site or per-post policies like allow, deny, teaser previews, and 402 payment-required responses. It also publishes AI-friendly endpoints like llms.txt, a JSON feed, and per-post Markdown.
Instead of blocking all bots or allowing unrestricted access, you can:
<ul>
<li>See AI bot traffic – Local-only analytics showing which bots are crawling your site</li>
<li>Verify bot identity using cryptographic signatures (RFC 9421)</li>
<li>Show teasers to unverified bots (first N words)</li>
<li>Rate limit bot access per agent</li>
<li>Whitelist/blacklist specific bots</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Bot Traffic Analytics – See which AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) are visiting your site</li>
<li>Signature Verification – Verifies RFC 9421 HTTP Message Signatures using Ed25519 cryptography</li>
<li>Content Teasers – Show first N words to unverified bots with customizable per-post settings</li>
<li>Rate Limiting – Per-agent rate limits with configurable time windows</li>
<li>Access Control – Whitelist/blacklist with wildcard pattern matching</li>
<li>Local Analytics – Visual dashboard with charts, stats cards, and decision breakdowns (no external tracking)</li>
<li>AI-Ready Endpoints – Serve llms.txt, JSON feed, and markdown for AI crawlers</li>
<li>Tabbed Admin Interface – Clean organization with Analytics, AI Endpoints, and Configuration tabs</li>
</ul>
<h4>AI-Ready Endpoints</h4>
OpenBotAuth provides machine-readable endpoints for AI systems:
<ul>
<li>/llms.txt – Standardized AI feed discovery (also at /.well-known/llms.txt)</li>
<li>/.well-known/openbotauth-feed.json – JSON list of all published posts</li>
<li>/.well-known/openbotauth/posts/{ID}.md – Per-post markdown content</li>
</ul>
Configure which post types to include (posts, pages, or custom types) and set the feed limit (up to 500 items). All data is served locally from your WordPress database. No external tracking or telemetry. Only published, non-password-protected posts are exposed.
<h4>How It Works</h4>
<ol>
<li>AI agent signs HTTP request with its private key (RFC 9421 signature)</li>
<li>WordPress plugin extracts signature headers and sends them to a verifier service</li>
<li>Verifier fetches agent’s public key from registry and verifies signature</li>
<li>Plugin applies policy: allow full content, show teaser, require payment, or deny</li>
</ol>
<h4>External Service Disclosure</h4>
This plugin connects to an external verifier service. When a signed bot request is received, the plugin sends the following data to your configured verifier URL via <code>wp_remote_post</code>:
<ul>
<li>HTTP method (GET, POST, etc.)</li>
<li>The accessed URL (including query string, if present)</li>
<li>HTTP signature headers (Signature, Signature-Input, Signature-Agent)</li>
<li>Additional HTTP header values explicitly listed in the Signature-Input header (e.g., content-type, accept, user-agent)</li>
</ul>
Privacy protection: Sensitive headers (cookies, authorization, proxy-authorization, www-authenticate) are NEVER forwarded, even if present in the request. If a bot’s signature covers a sensitive header, verification will fail with a clear error.
No WordPress user accounts or personal data is transmitted. Only the headers explicitly covered by the bot’s signature are forwarded to enable cryptographic verification. Note that the URL may include query parameters depending on your site’s structure.
You can: 
* Use the hosted verifier at <code>https://verifier.openbotauth.org/verify</code> 
* Self-host the verifier service (see documentation) 
* The verifier service may log requests server-side depending on your configuration
Analytics are local-only. Decision counts (allow/teaser/deny/pay/rate_limit) and bot traffic observations (User-Agent based) are stored in your WordPress database. No analytics data is sent to external servers.
For more information, please review our <a href="https://openbotauth.org/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://openbotauth.org/privacy" rel="nofollow ugc">Privacy Policy</a>.
<h3>Developer Hooks</h3>
<h4>Filters</h4>
openbotauth_policy 
Modify policy before applying:
<pre><code>add_filter('openbotauth_policy', function($policy, $post) {
 if ($post->post_type === 'premium') {
 $policy['price_cents'] = 1000;
 }
 return $policy;
}, 10, 2);
</code></pre>
<h4>Actions</h4>
openbotauth_verified 
Triggered when a bot is verified:
<pre><code>add_action('openbotauth_verified', function($agent, $post) {
 error_log("Bot {$agent['jwks_url']} accessed post {$post->ID}");
}, 10, 2);
</code></pre>
openbotauth_payment_required 
Triggered when 402 is returned:
<pre><code>add_action('openbotauth_payment_required', function($agent, $post, $price) {
 // Track payment requests
}, 10, 3);
</code></pre>
<h4>AI Endpoint Filters (v0.1.2+)</h4>
openbotauth_should_serve_llms_txt 
Disable llms.txt endpoint (e.g., when using Yoast):
<pre><code>add_filter('openbotauth_should_serve_llms_txt', '__return_false');
</code></pre>
openbotauth_should_serve_feed 
Disable JSON feed endpoint:
<pre><code>add_filter('openbotauth_should_serve_feed', '__return_false');
</code></pre>
openbotauth_should_serve_markdown 
Disable markdown endpoints:
<pre><code>add_filter('openbotauth_should_serve_markdown', '__return_false');
</code></pre>
openbotauth_feed_item 
Modify feed items:
<pre><code>add_filter('openbotauth_feed_item', function($item, $post) {
 $item['custom_field'] = get_post_meta($post->ID, 'my_field', true);
 return $item;
}, 10, 2);
</code></pre>
openbotauth_markdown_content 
Post-process markdown output:
<pre><code>add_filter('openbotauth_markdown_content', function($markdown, $post) {
 return $markdown . "\n\n---\nCopyright notice here";
}, 10, 2);
</code></pre>

OpenBotAuth – AI Crawler Access Control

Verify AI crawlers with HTTP Signatures and enforce allow/deny/teaser policies; also serves llms.txt and AI-ready feeds.

Gurjeet Singh

TechBeeps Services

The latest version introduces LLMS.txt Generator, allowing you to generate Learning Language Model Settings (LLMS) files for fine-tuning or prompt engineering setups.
AutoReply AI is a cutting-edge, intelligent WordPress plugin designed to automatically generate human-like replies to user comments, ensuring context-aware, engaging, and meaningful interactions on your website. By leveraging advanced AI models, AutoReply AI can analyze the content of user comments, identifying their relevance, intent, and context, before generating smart, personalized responses that feel genuine and natural. Whether your site hosts blogs, forums, or community-driven discussions, AutoReply AI adds value by ensuring that every interaction is well-informed and in tune with the conversation.
<h3>Key Features:</h3>
<ul>
<li>
LLMS.txt Generator: Create a structured <code>llms.txt</code> file designed for AI models and LLM systems. Supports:
<ul>
<li>Automatic mode: Auto-generates content from posts (custom post supported), pages, taxonomies, and site meta</li>
<li>Manual mode: Full user control over file contents via settings panel</li>
<li>Real-time preview and clean admin UI</li>
</ul>
</li>
<li>
Context-Aware AI Replies: AutoReply AI doesn’t just generate generic responses. It fully understands the context, tone, and subject matter of each comment to deliver relevant and thoughtful replies, making the conversation feel authentic and personalized.
</li>
<li>
Supports Multiple Platforms: The plugin is compatible with several WordPress-based discussion platforms, including native WordPress comments, BuddyPress, wpForo, ForumWP, Asgaros Forum, and bbPress, allowing you to engage your community no matter where they interact.
</li>
<li>
Advanced Spam Detection & Content Filtering: AutoReply AI comes with built-in spam detection and abusive content filtering, helping ensure that only legitimate comments receive replies. The plugin automatically detects and filters out gibberish, promotional content, offensive language, and low-quality comments, creating a clean, respectful, and trustworthy comment section.
</li>
<li>
AI-Driven Response Customization: Tailor the behavior of the AI to fit your website’s tone and personality. Whether you want your replies to be casual, formal, or humorous, you can customize the response style to align with your brand’s voice. With AutoReply AI, your replies will always sound like they belong.
</li>
<li>
Human-Like Conversations: The plugin uses state-of-the-art AI models, like OpenAI’s GPT-4 and Google’s Gemini, to generate highly convincing, human-like responses. This helps foster engagement and encourages more meaningful interaction with your audience.
</li>
<li>
Real-Time AI Responses: As soon as a user leaves a comment, the plugin will instantly generate and post a response, ensuring that your site always maintains active engagement and immediate responses to user input, fostering a lively community.
</li>
<li>
Security and API Key Protection: AutoReply AI prioritizes security, ensuring that your API keys are stored safely and encrypted. You can rest easy knowing your OpenAI and Gemini API keys are never exposed to unauthorized access.
</li>
<li>
Efficient and Lightweight: The plugin is designed to be lightweight, ensuring it doesn’t slow down your site. With minimal server resources needed, AutoReply AI runs smoothly in the background, delivering rapid, real-time AI responses without compromising site performance.
</li>
<li>
Easy Setup: Getting started with AutoReply AI is simple. Just install the plugin, enter your API key, configure the settings, and you’re good to go. It’s perfect for both beginners and advanced users.
</li>
<li>
Customizable Response Limits: You can fine-tune the word limit and length of the AI-generated responses, ensuring they meet your content guidelines. Whether you prefer concise replies or more detailed interactions, AutoReply AI can adjust to your needs.
</li>
</ul>
Supported AI Models: 
– OpenAI Models: GPT-4o-mini, GPT-4o, GPT-3.5-turbo, GPT-4-turbo, GPT-4 
– Gemini Models: Gemini 2.0 Flash-Lite, Gemini 2.0 Flash, Gemini 1.5 Flash, Gemini 1.5 Pro, Gemma 3
Features: 
– Generate AI-optimized llms.txt file for site metadata 
– Automatic and manual modes for LLMS file creation 
– Real-time content preview and modern UI 
– Auto-replies to comments using AI 
– Supports WordPress comments, BuddyPress, wpForo, ForumWP, Asgaros Forum, and bbPress 
– Now supports both OpenAI and Google Gemini APIs 
– Customizable AI behavior 
– Secure API key storage 
– Lightweight and efficient
<h3>External Services</h3>
improve admin settings.
<ol>
<li>
OpenAI API (https://api.openai.com/v1/chat/completions)
<ul>
<li>What it does: Generates AI-based responses. </li>
<li>Data sent: The user’s message query and API key. </li>
<li>Terms of Service: https://openai.com/terms </li>
<li>Privacy Policy: https://openai.com/privacy </li>
</ul>
</li>
<li>
Google Gemini API (<code>https://generativelanguage.googleapis.com/v1beta/</code>)
<ul>
<li>What it does: Generates AI-based responses </li>
<li>Data sent: The user’s message query and API key </li>
<li>Terms of Service: https://ai.google.dev/terms </li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
</li>
</ol>

AutoReply AI & LLMS.txt Generator

Gurjeet

Generate an llms.txt file to help LLMs understand your site. Supports auto/manual modes and live preview. Auto-reply to comments using AI.

OpenBotAuth – AI Crawler Access Control vs AutoReply AI & LLMS.txt Generator