Believintech Post Sync for Airtable vs Recognyze.AI

Believintech Post Sync for Airtable connects your Airtable base to WordPress and lets you create or update posts in a dedicated Custom Post Type from your Airtable records. Watch the demo video: https://youtu.be/6ZNXy5aweT0 Features include: Save Airtable Base ID, Table ID or Name, and API Token from the WordPress admin. Fetch the column list from your Airtable table. Map each Airtable column to a WordPress post field (Title, Description, Featured Image, or Meta Field). Create new posts or update existing posts in the bptsa_air_sync Custom Post Type when records are synced. Map every fetched Airtable column to a WordPress field. This plugin is not affiliated with, endorsed by, or sponsored by Airtable. “Airtable” is a trademark of Formagrid, Inc., used here only to describe the service this plugin connects to. External services This plugin connects to the Airtable REST API (https://api.airtable.com/v0/) to read records from your Airtable base and create or update them as posts inside WordPress. What the service is used for: The Airtable API is used to fetch the columns and records of the Airtable base you configure, so the plugin can map and synchronize them into a WordPress Custom Post Type (bptsa_air_sync). What data is sent and when: The plugin sends your Airtable Personal Access Token (as a Bearer token), the configured Base ID, and the configured Table ID or Name in the URL/query of each request. Requests are sent only when a logged-in WordPress administrator explicitly clicks Fetch Airtable Columns Data or Create or Update Records on the plugin settings page. No WordPress data is sent to Airtable. This service is provided by Airtable (Formagrid, Inc.): Terms of Service: https://www.airtable.com/company/terms-and-policies Privacy Policy: https://www.airtable.com/company/privacy

Recognyze.AI is a WordPress plugin for publishers who want to protect content, monetize AI usage, and control how agents access their site. Use the dashboard to sign posts in bulk, connect securely to the Recognyze Publisher API, and monitor signed and unsigned access-including Bot Wall blocks and optional Markdown for AI agents. Key Features Content Protection: Cryptographic signatures that verify authenticity and register content with Recognyze Post Management Dashboard: Overview of recognized, pending, and bulk sign/sync actions AutoRecognyze: Optionally recognize new Posts and Pages automatically on publish (Essentials settings) API Integration: Connect with your Recognyze account; API keys are encrypted at rest (AES-256-GCM when OpenSSL is available) API Key Rotation: Automatic rotation before expiry (14-day buffer), manual “Rotate now”, and visible key ID/expiration in Essentials Bot Wall (Agents & Bot Access): Rules-driven blocking for AI crawlers with per-bot and per-category controls (HTML/Markdown), powered by portal Bot Rules AI Bot Detection: Track signed and unsigned visits, including blocked Bot Wall requests and bot attribution metadata Access Logs: Logging for signed content access with event-based export and retention cleanup Unsigned Access Logs: Track unsigned content access and bot-like traffic separately Bulk Operations: Sign or synchronize many posts at once Encrypted Storage: API keys stored encrypted; Basic Auth credentials used only once to obtain a key and are never saved Export Functionality: Export access logs to Recognyze when batch size or time-based conditions are met Markdown for Agents: Serve content as Markdown via .md URLs or Accept: text/markdown, with Recognyze frontmatter, verify URLs, usage fees in points, and token estimates Use Cases Content creators who want to protect their intellectual property Publishers who want to monetize AI usage of their content Bloggers who want to track which AI systems access their content News organizations managing content licensing for AI training Any WordPress site owner concerned about AI crawler access Technical Features Supports multiple post types (posts, pages, and configurable types) RESTful Publisher API integration with optional dev-mode custom endpoint URL API key lifecycle (includes/api-key-rotation.php): metadata sync via GET /account/publisher/api-keys/current/, scheduled and manual PUT rotate Bot Rules cache with daily refresh from the Recognyze portal Optional softmax IP + User-Agent attribution for Bot Wall when portal ipVerification data is available Comprehensive access logging with event-based export and cleanup Scheduled tasks for log cleanup, export, API key metadata sync, and Bot Rules refresh Developer-friendly with hooks and filters (e.g. wprc_api_key_rotation_buffer_days) WordPress Coding Standards compliant Markdown for Agents (includes/markdown-for-agents.php): Content negotiation for text/markdown, YAML frontmatter with Recognyze id, verify_url, usage_fee (points), content_length, markdown_tokens; optional signed-only mode; Link header for alternate type Token estimator (includes/token-estimator.php): In-plugin token count for Markdown body (word/char heuristic), exposed as X-Markdown-Tokens header and in frontmatter Privacy & Data This plugin collects access logs that may include IP addresses, user agents, and timestamps. These logs are stored in your WordPress database and automatically exported and cleaned up based on export conditions (batch size or time interval). See the Privacy Policy section in Settings for more details. Support & Documentation For detailed documentation, API information, and support, visit Recognyze.AI Privacy Policy Recognyze.AI collects and stores the following data: Access Logs: When visitors access your signed content, the plugin may log: * IP address * User agent * Timestamp * Referrer URL * Post ID accessed Unsigned / Bot Wall logs: When enabled, the plugin may also log unsigned visits and Bot Wall blocks (including bot identity metadata where configured). API key metadata: Key ID, name, status, and expiration date (not the secret) are stored locally to support rotation scheduling. Storage: All data is stored in your WordPress database on your server. Retention: Logs are automatically exported and cleaned up from the database based on export conditions (batch size reached or 120-minute fallback interval). Exported logs are removed immediately after successful export. Export: If configured, access logs may be exported to external systems via API. User Rights: Site administrators can manually delete logs at any time from the Access Logs pages. Third Party Services: When you sign content, metadata is sent to the Recognyze.AI API. See the Recognyze.AI Privacy Policy for details on how this data is handled. Support For support, documentation, and feature requests: Website: https://recognyze.ai Documentation: https://www.recognyze.ai/publishers/wordpress/ Support: https://www.recognyze.ai/contact-us/