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.