AXIAL Audio Post Narration

By Axial Global LLC

★ 5.0/5 (2 ratings)0+ active installationsVersion 1.3.12

Add AI-generated audio summaries and full-read narration to WordPress posts through the AXIAL audio API.

Description

AXIAL Audio Post Narration connects WordPress to the AXIAL Nebula Audio service and lets editors generate audio for already-published content.

The plugin supports two audio modes, selected in the Nebula API configuration:

  • Audio summary: Nebula prepares a shorter spoken version of the post.
  • Full reading: Nebula prepares the complete article for natural narration without intentionally summarizing it.

Enable optional dual-player mode to generate and display both audio modes on one post, each using its own configured API. Choose each player placement independently (before/after content, floating bottom bar, or shortcode), with 1x / 1.2x / 1.5x playback speeds (1.2x default). The original single-player interface remains available when dual mode is disabled.

The generated audio can be downloaded into the WordPress Media Library and displayed with an accessible audio player.

Language-aware narration:

  • The language of each post is determined automatically. For translations created by AXIAL Post Translator, the translation’s saved language metadata takes precedence; otherwise the WordPress site locale is used.
  • The detected two-letter language code is transmitted to AXIAL Nebula with the post being narrated. A manual language selector is not required.
  • The summary and full-reading modes each process the content of the selected post in its language. Language support and speech quality depend on the configured AXIAL Audio service and available voice/model.
  • Regenerate existing audio after updating if it was created in the wrong language; stored MP3 files are not translated retroactively.

Settings are available at Axial Components > Post Narration.

Step-by-step setup guide:
https://axial.ar/articulos-de-ayuda/guia-axial-post-narration-wordpress/

Frequently asked questions:
https://axial.ar/ayuda-preguntas-frecuentes/

The audio API endpoint defaults to https://axial.ar/apis/v1/audio-management and can be edited by the site administrator. Only connect to trusted HTTPS services because configured API credentials are sent to that endpoint.

Features include:

  • Optional compact audio-summary Play control positioned before the title in news cards and compatible Elementor listings; displayed only when an audio summary is available.

  • Optional dual playback: separate summary and full-article MP3s for the same post.

  • Independent API and placement settings for each player.
  • Shortcodes [nebula_audio_resumen] and [nebula_audio_completo] for manual placement.

  • Configure multiple Nebula Audio APIs, each with its own identifiable name.

  • Select which API to use from each post editor; different APIs can use different voices or audio rules.
  • Choose one default API for automatic generation, bulk actions, and batch generation.
  • Estimate the credits required for a post with its selected Audio API before generating audio.
  • Generate audio from existing published posts.
  • Optional automatic generation when a post is published.
  • Generate audio for multiple existing posts.
  • Local validation to avoid sending posts that contain no useful editorial text.
  • Optional local MP3 copy in the Media Library.
  • Accessible floating player with play/pause, duration, and 1x / 1.2x / 1.5x playback speeds on standard pages; default speed is 1.2x, with visitor preference preserved.
  • AMP-compatible playback using native amp-audio actions (Play/Pause) without custom JavaScript.
  • Configurable player accent, background, and text colors.
  • Placement before content, after content, as a floating player, or through the [nebula_audio] shortcode.
  • Background status polling for asynchronous Nebula jobs.
  • Manual “Check status now” action from the post editor.

An AXIAL Nebula account, a Nebula Audio API key, and available service credits are required for audio generation. The WordPress plugin itself does not contain a paid-code unlock or local feature trial; charges apply to the external Nebula service.

Create an AXIAL account:
https://axial.ar/es/register/

AXIAL website:
https://axial.ar/

External service

This plugin depends on the external AXIAL Nebula Audio service to generate audio.

Service endpoint used by the plugin:
https://axial.ar/apis/v1/audio-management

When an authorized editor requests audio generation, the plugin sends the following data to AXIAL Nebula:

  • The configured AXIAL/Nebula account email.
  • The configured Nebula API key in the Authorization header.
  • The WordPress post title.
  • The WordPress post content.
  • The post excerpt when the configured API uses Audio summary mode.
  • The detected post language code (for example, en or es), derived from translation metadata or the WordPress locale.
  • A request identifier used to avoid duplicate generation requests.
  • The site URL as part of the HTTP User-Agent string.

This data is sent only when the plugin needs to query API capabilities, estimate/generate audio, or retrieve the result of a previously requested job. If local audio storage is enabled, the plugin also downloads the generated audio URL returned by Nebula into the WordPress Media Library.

The external service may consume paid credits according to the user’s AXIAL/Nebula account and API configuration.

Service provider:
https://axial.ar/

Privacy policy:
https://axial.ar/politica-de-privacidad/

Privacy

The plugin itself does not add advertising or tracking scripts. It communicates with AXIAL Nebula only as required to authenticate, generate audio, check asynchronous job status, and retrieve generated audio. See the External service section for the exact data transmitted.

The plugin also adds suggested disclosure text to WordPress Settings > Privacy so site owners can include the integration in their own privacy policy when appropriate.

Installation

  1. Upload the plugin folder to /wp-content/plugins/ or install the ZIP from Plugins > Add New > Upload Plugin.
  2. Activate AXIAL Audio Post Narration.
  3. Create or use an AXIAL Nebula account.
  4. Create one or more APIs of type Audio in AXIAL Nebula. Each API may use a different audio mode, voice, or editorial rules.
  5. Copy each API key when it is created.
  6. In WordPress, open Axial Components > Post Narration.
  7. Add each API with an identifiable name, account email, and API key.
  8. Choose the default API and use Test on each connection. Testing saves the current form before contacting Nebula.
  9. Configure post types and player behavior.
  10. Open a published post, choose the desired API, and click Calcular créditos to estimate the cost.
  11. Click Generate audio when you are ready.

FAQ

Do I need an AXIAL Nebula account?

Yes. Audio generation is performed by the external AXIAL Nebula service and requires an account, an Audio API key, and available service credits.

Does the plugin send my whole WordPress database to Nebula?

No. For audio generation it sends the configured account information plus the title and editorial text of the specific post being processed. In Audio summary mode, the excerpt may also be sent.

Can I use different voices on the same WordPress site?

Yes. Configure multiple Nebula Audio APIs and assign a different voice to each API in AXIAL Nebula. Give each connection a clear name in WordPress, then choose the desired API from the post editor before generating or regenerating audio.

Which API is used for automatic or bulk generation?

The API marked as default is used for automatic generation, WordPress bulk actions, and batch generation. Manual generation from an individual post lets the editor choose any configured API.

Can I generate audio for old posts?

Yes. Open any supported published post and use Generate audio, use the bulk action in the post list, or use the “Generate missing” tool in the plugin settings.

What happens if a post only contains a video or embed?

The plugin performs a local text check before requesting generation. Posts without enough useful editorial text are marked accordingly and are not sent for audio generation.

Does manual generation depend on WP-Cron?

The initial manual request is sent to Nebula immediately. Background polling, automatic generation, and staggered batch generation use WordPress scheduled events. If scheduled events are delayed on your site, you can use Check status now from the post editor after a job has been accepted by Nebula.

Can I use an existing MP3 instead of generating audio with Nebula?

Yes. From the post editor you can upload or choose an existing MP3 from the WordPress Media Library and associate it with that post. The frontend player will use the associated file just like a generated audio file.

Can editors download the audio directly from the post editor?

Yes. When a post has an associated audio file, the editor shows a Download MP3 button so the file can be downloaded without opening the Media Library.

Where is the generated audio stored?

By default the plugin downloads the generated MP3 to the WordPress Media Library. This can be disabled in the plugin settings.

Can I hide the visible player text?

Yes. The visible button label can be left blank. The player keeps accessible labels for screen readers.

What shortcode can I use?

Use [nebula_audio] in the current post. You can also specify a post ID with [nebula_audio id="123"].

Screenshots

Changelog

1.3.12

  • Automatically detect the language of each post, including AXIAL Post Translator translations.
  • Send the detected language to AXIAL Nebula Audio when requesting generation.
  • Include the language in the request identity to prevent reusing generated audio for a different language.
  • Align plugin version, internal asset version and WordPress.org stable tag.

1.3.10

  • Add an optional compact audio-summary Play control in news cards, positioned before the card title.
  • Support Elementor Posts, Loop Grid, WordPress query listings, and compatible custom news cards.
  • Resolve custom card posts through their permalink when the post ID is not present in the markup.
  • Load card playback on WordPress pages that contain post listings.
  • Show the control only for published posts with an available audio summary; do not substitute full-article narration.
  • Keep card playback independent of navigation links and synchronize play/pause with other audio.
  • Preserve existing single-post audio players, narration generation, API settings, and audio metadata.

1.3.5

  • Restore the independent floating player when summary and full-audio modes use different placements.
  • Keep floating narration controls separate from the shared inline translation toolbar.

1.3.2

  • Keep playback modes visible and narration controls separate from language navigation.

1.3.1

  • Redesign the audio bar with progress, time display, and speed selection.
  • Support a unified player with Summary and Full controls when both narrations are present.

1.2.9

  • Align release metadata with the plugin version and include AXIAL Components administration.
  • Preserve multiple audio API connections and independent narration modes.

1.2.6

  • Move administration to Axial Components > Post Narration.
  • Add setup guides, FAQ links, and configurable trusted HTTPS service endpoint.

1.2.3

  • Add optional dual playback with independent summary and full-text APIs.
  • Add [nebula_audio_resumen] and [nebula_audio_completo] shortcodes.
  • Add independently configurable player placement and playback speed controls.

1.1.2

  • Add per-post credit estimation.

1.1.1

  • Allow editors to upload/select an existing MP3 and download associated audio.

1.1.0

  • Add multiple audio APIs, default API selection, and per-post API assignment.

1.0.1

  • Add AMP-compatible audio playback using native amp-audio actions.

1.0.0

  • Initial release of AXIAL Audio Post Narration.