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

# Revelator Music API

API for managing music distribution accounts, artists, analytics, and related lookups on the Revelator platform. The API exposes 29 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically create a child account, user, and entities, modify account tier. Covers 29 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create a child account, user, and entities
- Modify account tier
- Authenticate a user and obtain a bearer token
- Update a user
- Get user identifiers by email
- Initiate password recovery

## Use cases

### Analytics Operations

Use the Revelator Music API to perform analytics operations programmatically. The API provides 29 endpoints covering core functionality including create a child account, user, and entities, modify account tier, authenticate a user and obtain a bearer token.

Example prompt: Call POST `/partner/account/signup` to create a child account, user, and entities

### Automated AccountManagement Management

Automate accountmanagement operations by combining multiple Revelator Music API endpoints. Agents can modify account tier and then authenticate a user and obtain a bearer token in a single workflow.

Example prompt: Call POST `/partner/account/upgrade` to modify account tier, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Revelator Music API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'create a child account, user, and entities', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/partner/account/signup` | Create a child account, user, and entities |
| POST | `/partner/account/upgrade` | Modify account tier |
| POST | `/partner/account/login` | Authenticate a user and obtain a bearer token |
| POST | `/partner/users` | Update a user |
| GET | `/partner/users` | Get user identifiers by email |
| GET | `/partner/invitation` | Get invitation information |
| POST | `/account/forgotpassword` | Initiate password recovery |
| GET | `/enterprise/clients/{enterpriseId}` | Get client information by enterprise ID |

## Key resources

- **AccountManagement** — Account signup, login, and tier management
- **UserManagement** — User lookup, update, and invitation endpoints
- **Enterprise** — Enterprise and client management
- **Lookups** — Reference data for currencies, countries, genres, stores, etc.
- **Artists** — Artist CRUD operations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 63 / 100
  - AI Discoverability: 62 / 100
- **View full report:** https://jentic.com/apis/revelator.com/revelator/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Revelator Music API by hand means handling two auth paths, a partner API key in the Authorization header and a JWT bearer token from its login endpoint, targeting the api.revelator.com host, and managing account and user calls yourself. Through Jentic you install once, import Revelator Music API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Revelator Music API puts the enterprise id in the URL path (`/enterprise/clients/{enterpriseId}`), so a rule can pin your agent to one enterprise's clients: it can read those clients and nothing else. You choose the operations it may call, so actions like account signup or upgrade are not included unless you add them.
- **Credential handling:** Your Revelator Music API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a child account and user' or 'list enterprise clients', and Jentic returns the matching Revelator Music API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Revelator Music API use?

The Revelator Music API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a child account, user, and entities with the Revelator Music API?

Yes. Use the POST `/partner/account/signup` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Revelator Music API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a child account, user, and entities through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a child account, user, and entities'. Jentic returns the matching Revelator Music API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Revelator Music API have?

The Revelator Music API exposes 29 endpoints covering accountmanagement, usermanagement, enterprise operations.

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

Yes. Because you run Jentic One yourself, you decide which Revelator Music API operations your agent may call and which credentials it may use. Since the enterprise id sits in the URL path (`/enterprise/clients/{enterpriseId}`), you can pin the agent to a single enterprise's clients so it reads those records and nothing else. Higher-impact actions like account signup (POST `/partner/account/signup`) or tier upgrade (POST `/partner/account/upgrade`) stay off-limits unless you explicitly add them.