Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / DataLakeStoreFileSystemManagementClient
DataLakeStoreFileSystemManagementClient logo

Microsoft Azure DataLakeStoreFileSystemManagementClient

Browse all Azure APIs
44
AI ReadinessFoundational (D)44/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageObject Storagenone3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Append data concurrently, set file expiry, and check access on files in an Azure Data Lake Store Gen1 account using its WebHDFS-compatible endpoint.

Use for: Append a batch of records to a streaming file in Data Lake Store, Set an expiry time on a temporary file in Data Lake Store, Check whether the current identity can read a Data Lake Store path, I need to mark a Data Lake Store file for automatic deletion

Not supported: Does not provision Data Lake Store accounts, manage U-SQL jobs, or run analytics queries - use for the WebHDFS extension operations on a Data Lake Store Gen1 account only.

Jentic publishes the only available OpenAPI specification for DataLakeStoreFileSystemManagementClient, keeping it validated and agent-ready. The API exposes the WebHDFS-compatible filesystem layer of an Azure Data Lake Store Gen1 account, focused on the extensions that matter for agent workflows: concurrent append, file expiry, and access checks. It is reached at the per-account endpoint and complements the standard WebHDFS verbs published by the underlying service.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the DataLakeStoreFileSystemManagementClient to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdatalakestorefilesystemmanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdatalakestorefilesystemmanagementclient" | 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 DataLakeStoreFileSystemManagementClient API.

Append data to a Data Lake Store file using the concurrent append extension

Set or clear an expiry time on a file in Data Lake Store

Check whether the caller has a given access permission on a file path

Reach the WebHDFS-compatible endpoint of a Data Lake Store Gen1 account

Use Data Lake Store extensions that go beyond standard WebHDFS verbs

Use Cases

Patterns agents use DataLakeStoreFileSystemManagementClient API for, with concrete tasks.

★ Concurrent ingestion to a Data Lake file

Multiple writers (a fleet of edge nodes or a parallel ingestion pipeline) need to append events to the same Data Lake Store file without coordinating writes. The concurrent append endpoint accepts batches from each writer and orders them server-side, so an ingestion controller can drive parallel writes safely.

Append a 4 KB batch of newline-delimited JSON events to '/raw/events-2026-06-10.jsonl' in the target Data Lake Store account using the ConcurrentAppend extension

Time-bound scratch files

Pipelines often write intermediate scratch files that should be cleaned up automatically. The file expiry endpoint lets the pipeline stamp a deletion time on a file at write time so the lake garbage-collects the artefact without an explicit delete step.

Set the expiry on '/scratch/job-1234/output.tsv' to 24 hours from now using the SetFileExpiry endpoint

Pre-flight access check

Before submitting a long-running U-SQL job that reads a list of paths, the controller verifies the calling identity has the required permission on each path. The CheckAccess endpoint reports whether the caller has the requested access mode on a path so the job is rejected early instead of failing mid-run.

Call CheckAccess on '/protected/finance' with mode 'r--' and confirm the current identity has read permission

Agent-driven safe write

An AI agent loading data into a partner's Data Lake Store first checks read access on the target folder, then concurrently appends the payload into a daily file, then stamps an expiry to enforce retention. Through Jentic, the agent chains these three operations using the same scoped credential without leaving the SDK.

Verify read access on '/inbound/partner-x', concurrently append the supplied payload to today's partner-x file, and set a 30-day expiry

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/WebHdfsExt/{path}

Concurrent append to a Data Lake Store file

PUT

/WebHdfsExt/{path}

Set the file expiry on a path

GET

/webhdfs/v1/{path}

Check access on a Data Lake Store path

POST

/WebHdfsExt/{path}

Concurrent append to a Data Lake Store file

PUT

/WebHdfsExt/{path}

Set the file expiry on a path

GET

/webhdfs/v1/{path}

Check access on a Data Lake Store path

Jentic AI Readiness Score

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.

D

DataLakeStoreFileSystemManagementClient

- Foundational (D)
44/100
50
Foundational Compliance
63
Developer Experience & Jentic Compatibility
19
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
50

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
86%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

19

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
77%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

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

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Azure Data Lake Store filesystem layer by hand means resolving the per-account host from the {accountName}.{adlsFileSystemDnsSuffix} template, obtaining an Azure AD bearer token for the Data Lake Store resource, and setting the correct WebHDFS op flag on every request yourself. Through Jentic you install once, import Data Lake Store FileSystem Management from the API Directory, store the Azure credential once, and your agent calls it.

Permission scoping

The filesystem API puts the file path in the URL (/WebHdfsExt/{path} and /webhdfs/v1/{path}), so a rule can pin your agent to specific path prefixes. You choose the operations it may call, so limit the agent to the ones it needs, such as ConcurrentAppend or CheckAccess, rather than adding the SetFileExpiry write when it only reads.

Credential isolation

Your Azure credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'concurrently append to a Data Lake Store file' or 'check access on a lake path', and Jentic returns the matching WebHDFS extension operation with its path parameter and required op flag so the agent calls it correctly.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DataLakeStoreAccountManagementClient

→

Manages the Data Lake Store account itself rather than its files

Pick this when the agent needs to provision or configure the account, not read or write files.

Complementary

DataLakeAnalyticsCatalogManagementClient

→

Browses U-SQL catalog metadata over Data Lake Store data

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

Alternative

DataShareManagementClient

→

Shares datasets across Azure subscriptions instead of writing to lake files

Pick this when the agent's goal is dataset sharing instead of low-level file writes.

FAQs

Specific to using DataLakeStoreFileSystemManagementClient API through Jentic.

Why is there no official OpenAPI spec for DataLakeStoreFileSystemManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataLakeStoreFileSystemManagementClient 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 Data Lake Store Filesystem API use?

The Data Lake Store Gen1 filesystem endpoint is gated by Azure Active Directory bearer tokens issued for the Data Lake Store 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 appears in the agent's context.

Can I append data to a single file from multiple writers with this API?

Yes. POST /WebHdfsExt/{path} with op=CONCURRENTAPPEND accepts payloads from concurrent writers and orders them server-side. This is the recommended pattern for parallel ingestion into a single Data Lake Store file without coordinating offsets between writers.

What are the rate limits for the Data Lake Store Filesystem API?

Data Lake Store Gen1 throttles by ingress and egress throughput per account rather than by request count, and returns 503 with a Retry-After hint when an account exceeds its provisioned throughput. Size individual append payloads to the documented 4 MB chunk limit and back off on 503 responses.

How do I set an expiry on a Data Lake Store file through Jentic?

Search Jentic for 'set file expiry data lake store', load the schema for PUT /WebHdfsExt/{path} with op=SETEXPIRY, then execute with expiryOption=Absolute or RelativeToNow and the desired expireTime. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Data Lake Store Filesystem API free?

There is no per-request charge for the filesystem extension calls themselves; you pay for storage and transactions in Data Lake Store Gen1 according to the standard Azure pricing for the service. Note that Gen1 has been retired in favour of ADLS Gen2 - new workloads should target Gen2 with its blob-compatible API.

Can I limit what my agent is allowed to do with the Data Lake Store Filesystem API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API puts the file path directly in the URL (/WebHdfsExt/{path} and /webhdfs/v1/{path}), so you can pin the agent to specific path prefixes. You also choose which operations it may call, so you can allow only ConcurrentAppend or CheckAccess and withhold the SetFileExpiry write when the agent only needs to read or append. The Azure credential is injected as a scoped bearer token at execution time and never enters the agent's prompt or logs.

GET STARTED

Start building with DataLakeStoreFileSystemManagementClient API

Explore with Jentic One
View OpenAPI Document