canonical: https://jentic.com/apis/audome.com/audome

# Audome API

Jentic publishes the only available OpenAPI specification for Audome API, keeping it validated and agent-ready. Audome is a workspace for audio teams that want to organise raw audio, project files, and the tag taxonomy used to describe them. The API exposes authentication, projects, file upload, and tag-list management so an external tool can ingest audio into an Audome workspace, attach the right tags, and read the project state back without using the web UI. With 12 endpoints it covers the full lifecycle of a project plus tag governance.

## For AI agents

Authenticate against an Audome workspace, create projects, upload audio files, and manage the tag lists used to describe them via Bearer tokens.

## Scope

Does not handle audio editing, mastering, or distribution - use for Audome project, file upload, and tag list management only.

## Capabilities

- Authenticate a workspace user via POST /authenticate to obtain a Bearer token
- Invalidate a session via POST /logout when an automation completes
- Create a new project for an audio engagement with POST /projects
- Upload an audio file to a project via POST /projects/{projectUuid}/files
- List, read, update, and delete tag lists used to describe audio assets
- Attach a tag to a tag list via POST /tag-lists/{taglistUuid}/tags/{tagUuid}
- Page through projects in the workspace with GET /projects

## Use cases

### Automated audio ingestion from a DAW or studio rig

Studios that record many sessions per week want raw audio to land in Audome the moment it is rendered. An ingestion script authenticates via POST /authenticate, creates a project per session via POST /projects, and uploads each rendered file via POST /projects/{projectUuid}/files. Files arrive in Audome organised by project without an engineer dragging them through the web UI.

Example prompt: Authenticate via POST /authenticate, create a project named 'Session 2026-06-09' via POST /projects, then POST /projects/{projectUuid}/files with the rendered WAV.

### Tag taxonomy governance

Audio teams use tag lists to describe sessions consistently. Over time tags drift and duplicates appear. The tag-lists endpoints let an admin script audit the workspace: GET /tag-lists returns the full taxonomy, PATCH /tag-lists/{taglistUuid} renames or merges, and DELETE /tag-lists/{taglistUuid} retires unused lists. POST /tag-lists/{taglistUuid}/tags/{tagUuid} attaches a tag to a list as part of a cleanup pass.

Example prompt: Call GET /tag-lists, identify any list with fewer than two tags attached, and DELETE /tag-lists/{taglistUuid} for each.

### Project status reporting

A producer wants a daily report of every active Audome project and how many files are attached to each. GET /projects paginates the workspace's projects, and GET /projects/{uuid} returns the file list per project. The agent assembles a CSV or Slack message with project name, owner, and file count without touching the Audome UI.

Example prompt: Page GET /projects, then for each project call GET /projects/{uuid} and emit a Slack message listing project name and file count.

### AI agent integration via Jentic

An audio-ops agent can use Jentic to upload audio into Audome without holding the Bearer token in prompt memory. The agent searches an intent like 'upload an audio file to an Audome project', Jentic returns the matching operation with its input schema, and the call is executed with the token resolved from your Jentic One instance. Authentication and refresh are handled by Jentic.

Example prompt: Use Jentic search 'upload audio to Audome', load the schema for POST /projects/{projectUuid}/files, and execute it for a known projectUuid with a multipart audio body.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /authenticate | Authenticate and obtain a Bearer token |
| POST | /logout | Invalidate a Bearer token |
| GET | /projects | List projects in the workspace |
| POST | /projects | Create a new project |
| GET | /projects/{uuid} | Get a specific project |
| POST | /projects/{projectUuid}/files | Upload an audio file to a project |
| GET | /tag-lists | List tag lists |
| POST | /tag-lists | Create a tag list |

## Key resources

- **Authentication** — Bearer token issuance and revocation via /authenticate and /logout
- **Projects** — CRUD over audio projects plus file upload into a project
- **Tag Lists** — CRUD over tag lists plus attachment of tags to a list

## Why Jentic

- **Setup:** Wiring Audome by hand means calling its authenticate endpoint for a bearer token, refreshing it on expiry, and tracking project uuids for uploads. Through Jentic you install once, import the Audome API from the API Directory, store the credentials once, and your agent calls it while Jentic manages the token.
- **Permission scoping:** Audome puts the project uuid in the URL path (/projects/{uuid}, /projects/{projectUuid}/files), so a rule can pin your agent to reads and file uploads for one project. You choose the operations it may call, so creating new projects is not included unless you add it.
- **Credential handling:** Your Audome workspace credentials and bearer token are stored once, encrypted, by your own Jentic One instance, which refreshes the token via the authenticate endpoint and injects it at execution time. The raw secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upload audio to Audome', and Jentic returns the matching operation with its input schema so the agent picks /projects, /projects/{projectUuid}/files, or /tag-lists without reading the reference docs.

## Related APIs

- **Auphonic API** — Auphonic is the closest peer for automated audio post-production and rendering APIs.
- **Dropbox API** — Dropbox often sits in front of Audome as the source of raw audio files to ingest.
- **Castos API** — Castos hosts and distributes podcast episodes once Audome has organised the source audio.

## FAQ

### Why is there no official OpenAPI spec for Audome API?

Audome publishes its API reference at app.audome.com/api-documentation but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Audome API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Audome API use?

The Audome API uses Bearer token authentication. POST /authenticate exchanges workspace credentials for a Bearer token, which is then sent in the Authorization header on every other request. Through Jentic the credentials and token are stored in the vault and injected at execution time.

### Can I upload an audio file to a project with the Audome API?

Yes. POST /projects/{projectUuid}/files accepts a multipart upload and attaches the file to the named project. Create the project first via POST /projects, then upload using the returned projectUuid.

### What are the rate limits for the Audome API?

Audome does not publish per-endpoint rate limits in the spec. Production integrations should pace bulk uploads against the file-upload endpoint and back off on 429 responses, which the platform returns when concurrent uploads exceed the workspace limit.

### How do I create a project and upload a file through Jentic?

Run jentic search 'create an Audome project', execute POST /projects, then run jentic search 'upload audio to Audome' and execute POST /projects/{projectUuid}/files with the returned projectUuid. Jentic resolves the Bearer token from the vault at execution time.

### Is the Audome API free?

API access is included in Audome's standard workspace plans rather than priced per call. A workspace must be on a plan that allows API access for the bearer token issued by /authenticate to be honoured.

### Can I limit what my agent is allowed to do with the Audome API?

Yes. Because you run Jentic One yourself, your own rules decide which Audome operations and credentials the agent may use. Audome puts the project UUID in the URL path (/projects/{uuid}, /projects/{projectUuid}/files), so a rule can pin the agent to reading and uploading files for a single project. Since you choose the exact operations it may call, creating new projects via POST /projects or deleting tag lists stays off unless you explicitly allow it.