WordPress
Your own WordPress site: agents read and publish posts, pages and media through its REST API.
Connect it with: User name and password. WordPress's own documentation: https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/.
What agents can do
Connect WordPress so the agents working your tasks can reach it. With it connected, they can:
- Draft, edit and publish posts and pages, including categories, tags and featured images.
- Upload images and files to the media library and use them in content.
- Read existing content, comments and users to answer questions or audit a site.
- Update custom post types and fields that plugins expose through the REST API.
Before you start
- A self-hosted WordPress site (WordPress 5.6 or later) reachable from the internet over https.
- A WordPress user with the role the agents need: Editor for content, Administrator only if they must change settings or plugins.
- Application Passwords enabled: they are on by default, but some security plugins (and sites served over plain http) turn them off.
- For a site on WordPress.com, use the WordPress.com integration instead.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with WordPress
Jaah connects to WordPress with a user name and password, not with a sign-in button.
Connect with an API key
Find each value first:
- Site URL: Your site's public address, starting with https:// - the address visitors type, without /wp-admin. If WordPress is installed in a subfolder, include it (https://example.com/blog).
- Username: The WordPress username the agent acts as - in wp-admin, Users > Profile, the Username field at the top (not the display name). Use an account with the Editor role unless agents must change settings.
- Application password: In wp-admin, open Users > Profile, scroll to Application Passwords, type Jaah in New Application Password Name and select Add New Application Password. Copy the 24-character password shown (spaces are fine) - WordPress shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the WordPress card.
- Name the secret and choose who can use it.
- Fill in Site URL, Username, Application password.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to WordPress with a user name and password, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls WordPress's API once (GET <Site URL>/wp-json/wp/v2/users/me?context=edit) with the stored values, and shows who it answered as, or which value WordPress refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: base_url, username, application_password.
Tell the agent in your task description which secret to use, for example “use the WordPress secret org/wordpress”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at WordPress once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at WordPress's side too, change the password at WordPress or remove the user.
Limitations
- The site must be reachable from the internet over https: Jaah refuses private, intranet and localhost addresses.
- Agents get exactly the WordPress role of the user whose application password you paste - there are no finer scopes.
- Plugins that block the REST API or Basic authentication (some security and firewall plugins, or a host's web application firewall) stop agents and the test alike.
- Agents can do only what the connected WordPress account allows.
Troubleshooting
Test says WordPress rejected the application password (401)
Check that Username is the login name from Users > Profile, not the display name or email, and that you pasted the application password rather than your normal password. If both are right, a security plugin or your host may strip the Authorization header: ask your host to pass it through to PHP, or allow Application Passwords in the plugin's settings.
There is no Application Passwords section on the profile page
The feature is off. It needs WordPress 5.6 or later and a site served over https; a security plugin can also disable it (look for an Application Passwords or REST API setting). Update WordPress, enable https, or switch the setting back on.
Test says WordPress cannot be reached at that address
Site URL must be the public https address of the site. Jaah never calls a private, intranet or localhost address, so a site only reachable on your company network or VPN cannot be connected.
Test answers 404 or says WordPress did not answer with an API response
Open your Site URL followed by /wp-json/ in a browser. If that is not a JSON page, permalinks are set to Plain or a plugin hides the REST API: in wp-admin open Settings > Permalinks, choose any option other than Plain and save.
Still stuck? Select Test and read the result: it names the value WordPress refused and the status it answered.
FAQ
Should I use my own WordPress account?
Better not. Create a dedicated user (for example jaah-agent) with the Editor role in Users > Add New User, and create the application password on that user: everything agents do is then attributed to it, and you can revoke it without touching your own login.
How do I revoke Jaah's access from WordPress?
In wp-admin open Users > Profile for the user, scroll to Application Passwords and select Revoke next to Jaah. Agents lose access immediately.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one WordPress account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.