Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →An AI integration can access WordPress data and actions that the site exposes through its APIs. Public content is generally available without signing in; private information and the ability to create, edit, or manage content depend on authentication, the account’s capabilities, endpoint permissions, and site-specific configuration. The word “AI” does not grant special access. To limit risk, use a dedicated, revocable credential over HTTPS, give its WordPress account only the capabilities required, and inspect the routes and actions enabled on your site.
What WordPress data can an AI integration access?
The WordPress REST API is a JSON interface to site resources. Its documented endpoint families include posts and revisions, pages and revisions, categories, tags, comments, taxonomies, media, users, post types, statuses, settings, themes, search, blocks, and plugins. Sites may also expose custom post types, metadata, or routes added by plugins and custom code.
That list describes what the API can support, not what every integration receives. A route’s existence does not mean a particular client can see every record or field. Authentication, the endpoint’s permission checks, the requesting account’s capabilities, and the site’s configuration determine what is available.
Public content and private information
WordPress Developer Resources describes the REST API as providing “public data accessible to any client anonymously, as well as private data only available after authentication.” Public content may therefore be accessible to an integration even if the site owner has not installed an AI plugin. Installing an integration is not what makes public pages public.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Private or password-protected content, internal user information, custom post types, and metadata are not automatically available to every API client. Their exposure depends on authentication and the site’s endpoint or configuration choices. Do not assume either that an AI integration receives a complete database dump or that private material is exposed: check the actual routes, permissions, and fields involved.
Read access versus actions
An authenticated integration may be able to do more than read. REST requests can support content-management actions, but whether a request succeeds depends on the account’s capabilities and the endpoint’s permission checks. Depending on the routes a site exposes, relevant resources can include content, media, settings, themes, or plugins; the API’s broad reference does not establish that a given account can change all of them.
Rank #2
- HARDWARE 2FA AND MFA: FIDO Alliance Certified FIDO2 v2.1 with CTAP2 plus legacy U2F and CTAP1 for strong two-factor login and passwordless sign-in on services that support security keys
- BUILDING ACCESS ON ONE CARD: MIFARE DESFire EV2 4K applet with AES encryption adds office door and physical access control alongside digital authentication
- CERTIFIED SECURE ELEMENT: An NXP Common Criteria EAL6+ certified secure controller and Java Card platform protects your keys on a tamper-resistant chip
- DUAL INTERFACE SMART CARD: Contactless NFC ISO 14443 plus ISO 7816 contact reader support in an ISO 7810 ID-1 format that is passive and needs no battery
- SWISS ENGINEERED DESIGN: Built by Cryptnox as a single card for authentication and access control and backed by a 2 year warranty
WordPress roles are groups of capabilities, and capabilities are the specific permissions WordPress or plugin code checks. For example, the official roles-and-capabilities documentation says manage_options permits viewing, editing, and saving site options, while Editors lack that capability by default. Roles and permissions can be customized, so a role label alone is not a reliable audit of an integration’s reach.
What determines an integration’s access?
There is no universal permission set for “an AI integration.” Its effective access comes from several layers working together:
Rank #3
- Ultra-Compact FIDO2 Security Key - Plug-and-stay or carry on a keychain. This USB-A hardware security key offers portable, always-on protection for desktop and mobile use. (Item Size: 0.75 X 0.74 IN x 0.25 IN)
- USB-A Hardware Key for All Devices - Works with USB-A ports on PC, Mac, Android, and other laptop/notebook device. Enables secure, cross-platform login with FIDO2.0 passkey support.
- FIDO Certified Security Key - Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
- Passwordless Login with Passkey - Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
- Advanced Multi-Factor Authentication - Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.
- Authentication: whether the request is anonymous or authenticated, and which WordPress account the credential represents.
- Account capabilities: the permissions assigned to that account, including any customizations made by the site or plugins.
- Endpoint permissions: the checks the API route makes before returning data or carrying out an action.
- Site-specific exposure: which plugin routes, custom post types, metadata, and other API features have been registered or enabled.
- Integration behavior: which routes and fields the particular integration requests and what it does with the results. WordPress access controls do not, by themselves, establish the vendor’s retention, training, or onward-sharing practices.
WordPress recommends checking user capabilities when plugin code accepts data or performs actions. That applies to custom integrations as well: the account’s permissions and the endpoint’s own checks both matter.
How can you protect WordPress data when connecting an AI service?
- Create a separate Application Password for each external integration. Application Passwords are per-application credentials for API authentication, rather than the user’s interactive login password. They are shown only when created, stored hashed by WordPress, and can be revoked. Availability can be disabled by a filter, plugin, or custom code.
- Use the credential only over HTTPS. Application Password authentication uses Basic Authentication, which sends credentials in an Authorization header. Without encryption, that header could be intercepted.
- Use a minimally capable WordPress account. Give the account only the capabilities needed for the integration’s specific task. Check the capabilities themselves rather than relying only on a role name; site and plugin customizations can change what a role can do.
- Keep the credential out of exposed locations. Store it in a protected secret store; do not put it in browser-side code or a public repository. This is practical guidance for protecting a reusable credential.
- Revoke credentials that are no longer needed. If you remove an integration or stop using it, revoke its Application Password rather than leaving it active.
- Inspect the site’s API exposure. Review the routes the site advertises, including plugin routes and custom resources, and check whether metadata is exposed. The available routes and data are installation-specific.
- Review endpoint checks and integration data handling. Check the permissions implemented for relevant routes or actions. Separately consult the integration provider’s privacy and security documentation for its retention, onward processing, and deletion practices; WordPress’s permission model cannot answer those vendor-specific questions.
Cookie authentication is for logged-in, same-origin use
For requests made within a logged-in WordPress session, cookie authentication is the standard method, and REST nonces help prevent cross-site request forgery. The REST API handbook states that a request without the nonce is treated as unauthenticated, even when the browser user is logged in. This is intended for same-origin use in WordPress, not as the general credential for an external application.
Rank #4
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
What does the WordPress Abilities API change?
The Abilities API is documented for WordPress 6.9 and above. It provides a registry for distinct site actions, with descriptions, input and output definitions, categories, and permissions. WordPress describes it as a standardized way to register and discover functionality; compatible external systems, including AI agents, can use it to discover and interact with registered capabilities. This does not mean every AI integration uses the API, or that sites on earlier WordPress versions have it.
For an ability to be listed and executable through REST, its registration must set show_in_rest to true; REST exposure is off by default. The endpoints require an authenticated user, and each ability’s permission callback controls execution. If your site uses the Abilities API, inspect both which abilities are exposed and what their permission callbacks allow. Discoverability alone does not establish that an action is safe or that every authenticated account may run it.
How do you assess a specific connection?
General WordPress documentation cannot identify the exact data a particular integration receives from a particular installation. Before connecting—or when reviewing an existing connection—check these site- and vendor-specific details:
- The site’s WordPress version and whether the relevant feature, including the Abilities API, is available.
- The API routes advertised by the site, including routes registered by plugins or custom code.
- Any custom post types and metadata exposed through the API.
- The account used by the integration and its effective capabilities.
- The permission checks for the routes or abilities the integration can call, including which abilities have
show_in_restenabled. - The integration’s own documented data scope, requested fields, available read and write actions, credential handling, and data-retention practices.
These checks distinguish what WordPress makes possible from what a specific connection actually requests and is permitted to do. If the provider does not clearly document its data handling, WordPress’s access controls cannot fill that gap.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
