DataLakeAnalyticsCatalogManagementClient

Name: DataLakeAnalyticsCatalogManagementClient API
Brand: DataLakeAnalyticsCatalogManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasenone45 EndpointsREST

For Agents

Browse and inspect the U-SQL catalog of an Azure Data Lake Analytics account — list databases, tables, views, schemas, assemblies, and ACLs, and manage credential entries.

Connect the DataLakeAnalyticsCatalogManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataLakeAnalyticsCatalogManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DataLakeAnalyticsCatalogManagementClient API.

List U-SQL databases, schemas, tables, and views in a Data Lake Analytics catalog

Inspect table schemas, table statistics, partitions, types, and table-valued functions

Retrieve assemblies, stored procedures, and external data sources for a database

Read and modify catalog ACLs at account and database scope

GET STARTED

Start building with DataLakeAnalyticsCatalogManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DataLakeAnalyticsCatalogManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for DataLakeAnalyticsCatalogManagementClient, keeping it validated and agent-ready. The API exposes the U-SQL catalog of an Azure Data Lake Analytics account so callers can browse and inspect databases, schemas, tables, views, table-valued functions, stored procedures, assemblies, credentials, and ACLs. It is read-oriented over the catalog plus credential mutation endpoints, and is the path agents use to discover the shape of analytics data before submitting jobs. All 45 operations live under the /catalog/usql/* path tree.

Use Cases

Patterns agents use DataLakeAnalyticsCatalogManagementClient API for, with concrete tasks.

★ Pre-job catalog inspection

Before submitting a U-SQL job to Azure Data Lake Analytics, an analyst or agent inspects the target catalog to confirm tables, schemas, and types match the job script. The catalog API returns database, schema, table, and column metadata so the job author can validate references against the live catalog instead of a stale data dictionary.

List all tables in the database 'sales' on the Data Lake Analytics account and return the column list for the table 'orders'

Catalog credential management for U-SQL jobs

U-SQL scripts that pull from external systems (Azure SQL Database, blob, etc.) need credential entries registered in the catalog. The credentials endpoints let an automation flow create, rotate, and delete those entries against a specific U-SQL database without manual portal steps.

Create a catalog credential named 'sql-prod-reader' on database 'sales' with the supplied user identity and password, then verify it appears in the credential list

Catalog ACL audit

Compliance checks routinely verify which principals have access to U-SQL databases. The ACL list endpoints return the full set of ACL entries at account or database scope so an audit script can reconcile actual permissions against an expected access matrix.

Retrieve the ACL list for database 'finance' and flag any principal that is not in the approved auditor allowlist

Agent-driven analytics catalog discovery

An AI agent asked to answer a business question against Data Lake Analytics first needs to know what data exists. Through Jentic, the agent searches for catalog discovery operations, lists databases and tables, then composes a U-SQL query against the resolved schema. The catalog API is the agent's source of truth for what U-SQL objects exist.

Discover all tables in databases on the Data Lake Analytics account that contain a column named 'customer_id' and return their fully qualified names

Key Endpoints

45 endpoints — jentic publishes the only available openapi specification for datalakeanalyticscatalogmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/catalog/usql/databases

List U-SQL databases in the catalog

GET

/catalog/usql/databases/{databaseName}

Get a specific U-SQL database

GET

/catalog/usql/databases/{databaseName}/schemas/{schemaName}/tables

List tables in a schema

GET

/catalog/usql/databases/{databaseName}/credentials

List catalog credentials in a database

GET

/catalog/usql/databases/{databaseName}/acl

List ACL entries for a database

GET

/catalog/usql/databases/{databaseName}/assemblies

List assemblies registered in a database

GET

/catalog/usql/databases/{databaseName}/procedures

List stored procedures in a database

GET

/catalog/usql/databases

List U-SQL databases in the catalog

GET

/catalog/usql/databases/{databaseName}

Get a specific U-SQL database

GET

/catalog/usql/databases/{databaseName}/schemas/{schemaName}/tables

List tables in a schema

GET

/catalog/usql/databases/{databaseName}/credentials

List catalog credentials in a database

GET

/catalog/usql/databases/{databaseName}/acl

List ACL entries for a database

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD bearer tokens for Data Lake Analytics are stored encrypted in the Jentic vault. Agents receive a scoped token at execute time and the underlying client secret or refresh token never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list u-sql databases') and Jentic returns the matching catalog operation with its input schema, so the agent calls the right endpoint without scraping documentation.

Time to first call

Direct integration with the Data Lake Analytics catalog, including AAD setup and account-specific URL handling, typically takes 1-3 days. Through Jentic: under 1 hour to search, load, and execute the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DataLakeStoreAccountManagementClient

Manages the underlying Data Lake Store account that backs an Analytics account

Choose this when the agent needs to provision or configure the Data Lake Store account itself rather than browse U-SQL catalog metadata.

Complementary

DataLakeStoreFileSystemManagementClient

Reads and writes raw files in Data Lake Store

Pick this when the agent needs file-level operations against the data lake rather than catalog metadata.

Alternative

DataShareManagementClient

Shares datasets across Azure subscriptions instead of querying a U-SQL catalog

Pick this when the agent needs to publish or subscribe to shared datasets rather than introspect a U-SQL catalog.

FAQs

Specific to using DataLakeAnalyticsCatalogManagementClient API through Jentic.

Why is there no official OpenAPI spec for DataLakeAnalyticsCatalogManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataLakeAnalyticsCatalogManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Data Lake Analytics Catalog API use?

The catalog client itself reaches an account-specific endpoint (typically https://{accountName}.azuredatalakeanalytics.net) and is gated by Azure Active Directory bearer tokens issued for the Data Lake Analytics resource. Through Jentic, the AAD credential is held in the encrypted vault and a scoped token is supplied at execute time so the bearer token never enters the agent's prompt context.

Can I list all tables in a U-SQL database with this API?

Yes. Call GET /catalog/usql/databases/{databaseName}/schemas/{schemaName}/tables to enumerate tables under a specific schema, or use the per-database listing endpoints to walk schemas first. Combined with the table-detail endpoint you can retrieve column lists, partitioning, and statistics for each table.

What are the rate limits for the Data Lake Analytics Catalog API?

Azure Data Lake Analytics applies subscription-level throttling rather than per-endpoint rate caps; sustained polling against catalog list endpoints can return HTTP 429 responses with a Retry-After hint. Treat the catalog as a metadata store and cache results for the duration of a job rather than calling list operations on every step.

How do I rotate a U-SQL catalog credential through Jentic?

Search Jentic for 'rotate u-sql catalog credential', load the schema for PUT /catalog/usql/databases/{databaseName}/credentials/{credentialName}, then execute with the new credential payload. The pip install jentic Python SDK uses the async search, load, execute pattern and reads JENTIC_AGENT_API_KEY from your environment.

Is the Data Lake Analytics Catalog API free?

There is no separate charge for catalog metadata calls beyond standard Azure Data Lake Analytics pricing — you pay for the underlying account, storage, and any U-SQL job hours consumed. Catalog reads do not bill per-request.