Your articles in audio, with no key to copy and no developer.

Install the plugin, click Connect, authorise it on our site. That is all. No API key to paste, no password handed to WordPress, no technical work.

After that your journalists publish as usual and the player appears at the top of the article. This is the path most of our customers take: they will never touch a line of API.

Free download, no account · WordPress 6.0 and above · PHP 7.4 and above · Gutenberg and classic editor

Three steps, about six minutes

Exactly what happens at each step, including what can go wrong.

1. 01Install

   2 min

   Nothing unusual here: the plugin installs and activates like the others, and it adds a single menu entry.

   • 01Plugins, then Add New, then search for WeDispatch. Install, Activate.
   • 02A WeDispatch menu appears in the admin sidebar.
   • 03No table is created in your database, and no file is written outside the plugin folder.
   • 04No request leaves for us before you have connected an account.
   If it does not work

   On an older installation, check for PHP 7.4 as a minimum. If your host blocks outbound connections, the plugin detects it and shows the address to allow, rather than failing in silence.

2. 02Connect

   1 min

   This is the step where you are usually sent off to fetch an API key. Not here.

   • 01Click Connect. WordPress opens our site in a new tab.
   • 02Create the free account, or sign in if you already have one. No card is asked for.
   • 03You see your site's name and what the plugin will be allowed to do. You authorise it.
   • 04Back in WordPress: the connection is established and the account name is shown. The key was exchanged server to server, and you never saw it.
   What this avoids

   A copied key always ends up lying around somewhere: an email, a chat thread, a notebook. Here there is nothing to mislay, and the key belongs to this site alone. You can revoke it from the dashboard without touching your other sites.

3. 03Publish

   3 min

   Pick automatic mode, publish or update an article, and listen. After that the plugin works without you.

   • 01Choose which content types are covered: posts, features, pages. You can exclude categories.
   • 02Automatic mode: every publication triggers generation. Manual mode: one button per article, to keep control.
   • 03Publish an existing article. The audio is ready in seconds for a news brief, under a minute for a long read.
   • 04The player appears at the top of the article, or wherever you placed the Gutenberg block.
   The classic trap

   If your theme filters content through an unusual hook, the player may not insert itself. In that case the Gutenberg block or the shortcode give you control over the exact position, and the diagnostics screen tells you what it detected.

Why you will never paste an API key

The usual method asks you to generate a key on one site, copy it, and paste it into WordPress. That key crosses a clipboard, sometimes an email, often an internal chat thread. It ends up living in clear text in a database several people administer.

We do it differently. WordPress opens our site, you authorise the connection with the account you have just created, and the plugin exchanges a single-use code for its own key, server to server. You never see the key, nobody copies it, and it belongs to this site alone.

One practical consequence matters more than it sounds: your site does not need to be reachable from outside. A staging site, an intranet or a password-protected site connects just as well as a public one.

What travels, and what does not

• NeverYour WordPress password. We do not see it and the plugin transmits it nowhere.
• NeverAn API key displayed, copied or pasted by a human being.
• NeverAn inbound connection to your site. Everything leaves from your end, so a staging site or an intranet works just as well.
• OnceA single-use code, valid for a few minutes, exchanged server to server for the site's key.
• ThenThe text of your articles, so it can be voiced, and nothing else. It trains no model.

You can revoke a site's connection from the dashboard at any time. The other sites are unaffected: each one has its own key.

Everything is configured inside WordPress, without changing tab

The plugin is not a thin bridge that sends you back to our site at the first setting. What the newsroom uses every day lives in the newsroom's own tool.

What changes for the newsroom: nothing

It is the only goal worth having. Journalists write and publish in WordPress exactly as before. The plugin works behind them.

Two other paths, exactly the same result

The choice depends on your setup, not on your budget: everything is included in the same subscription.

Questions from WordPress administrators

• Is the plugin free?

  Yes, and there is nothing to pay to install it or to try it. It connects to a WeDispatch account, whose free trial includes 5 credits, one credit being 1,000 characters. Beyond that the service is paid for; the plugin never is.

• Do I need an account to download it?

  No. The file downloads freely from this page. An account is only needed when you connect the site, that is, when you want to produce your first audio.

• Is this the latest version?

  Always. The archive is rebuilt from the plugin's source code on every download: this page cannot distribute a stale version, because it stores no file.

• Does the plugin slow my site down?

  Generation happens on our side, not on your server. For the visitor, the player is a one-line asynchronous script that blocks neither the page nor its first render.

• What happens if I deactivate the plugin?

  Your audio stays online and keeps being served, because it is not hosted inside WordPress. Only the automatic insertion of the player stops. Reactivate and everything comes back.

• Does it work on WordPress multisite?

  Yes. Each site on the network connects separately and receives its own key, while sharing the volume and the billing at account level.

• What about a staging site or an intranet?

  It works, because the connection leaves from your site towards us and never the other way. We do not need to reach your server, nor even to know its public address.

• Can I choose where the player appears?

  Three ways: automatic insertion at the top or bottom of the article, a Gutenberg block placed wherever you like, or a shortcode for the classic editor and theme templates.

• Is my content used to train a model?

  No. The text serves only to produce the audio. Charter mode even lets you guarantee that no language model touched your text, only its voicing.

• Does it work with my theme and my page builder?

  Yes. The player is placed by a block, a shortcode, or automatically at the top of the article, and it picks up your page's colours. It imposes neither a font nor a layout.