Agent-ready OpenAPI document · curated by JenticAnalyticsData PipelinesAWS Signature v4 (HMAC)44 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically manage DataBrew datasets, recipes, projects, and jobs to clean and transform data at scale.
Use for: I need to clean a CSV file in S3 with a DataBrew recipe, I want to schedule a recurring data preparation job, Create a DataBrew project for a sales dataset, Run a profile job to assess data quality
Not supported: Does not handle ad-hoc SQL querying, real-time streaming, or warehouse modeling - use AWS Glue DataBrew for visual recipe-based data preparation only.
Jentic publishes the only available OpenAPI specification for AWS Glue DataBrew, keeping it validated and agent-ready. AWS Glue DataBrew is a visual data preparation service for analysts and data scientists. The API manages datasets, projects, recipes (transformations), recipe jobs, profile jobs, schedules, and rulesets that enforce data quality. Recipes capture hundreds of cleaning, transformation, and feature-engineering steps as code, and jobs apply them at scale to data in S3, Redshift, Snowflake, and JDBC sources.
Install Jentic One Beta
Connect the AWS Glue DataBrew to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Glue DataBrew, 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%2Famazonaws.com%2Faws-databrew" | sh2
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%2Famazonaws.com%2Faws-databrew" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 AWS Glue DataBrew API.
Create datasets that point to S3, Redshift, JDBC, or Data Catalog sources
Author and version transformation recipes with hundreds of built-in steps
Run recipe jobs and profile jobs to apply transformations and assess data quality
Schedule recurring jobs and manage their concurrency and outputs
Validate data with rulesets that codify data-quality assertions
Tag, list, and delete projects, datasets, jobs, and recipes for housekeeping
Use Cases
Patterns agents use AWS Glue DataBrew API for, with concrete tasks.
★ Self-Service Data Cleaning for Analysts
Analysts need to clean and reshape datasets without writing Spark code. AWS Glue DataBrew lets them build a recipe visually, then save it via PublishRecipe and run it programmatically with CreateRecipeJob and StartJobRun. Recipes capture every step as code, making the work reproducible and reviewable.
Call CreateRecipeJob with DatasetName, RecipeReference {Name, RecipeVersion}, and an S3 output, then StartJobRun and poll DescribeJobRun until the run completes.
Profile Jobs for Data Quality Assessment
Data engineering teams profile incoming datasets to detect schema drift, null spikes, and distribution changes before downstream pipelines consume them. AWS Glue DataBrew's profile jobs sample data, compute statistics, and emit reports that integrate with rulesets for pass/fail data-quality gates.
Call CreateProfileJob with the dataset and an S3 output location, StartJobRun, then DescribeJobRun until COMPLETED to retrieve the profile statistics.
Scheduled Daily Data Preparation
ETL operations need recurring transformation jobs that prepare data for analytics every day. AWS Glue DataBrew's CreateSchedule attaches a cron expression to one or more jobs, and the service handles concurrency, retries, and notifications.
Call CreateSchedule with a CronExpression like 'cron(0 6 * * ? *)' and JobNames=['daily-clean'] to run the job every morning at 06:00 UTC.
Agent-Driven Data Quality Gates
An AI agent supporting a data team can run profile jobs, compare statistics against thresholds, and trigger downstream workflows. Through Jentic, the agent loads each operation by intent and chains CreateProfileJob, StartJobRun, DescribeJobRun, and CreateRuleset without writing boto3 plumbing.
Run a profile job, then call CreateRuleset with rules asserting completeness > 99% on key columns, and re-run the profile to validate.
Key Endpoints
44 endpoints — jentic publishes the only available openapi specification for aws glue databrew, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/datasets
Create a dataset
POST
/projects
Create a project binding a dataset to a recipe
POST
/recipes
Create a recipe
POST
/recipeJobs
Create a recipe job
POST
/profileJobs
Create a profile job
POST
/schedules
Create a schedule
POST
/rulesets
Create a data-quality ruleset
POST
/datasets
Create a dataset
POST
/projects
Create a project binding a dataset to a recipe
POST
/recipes
Create a recipe
POST
/recipeJobs
Create a recipe job
POST
/profileJobs
Create a profile job
POST
/schedules
Create a schedule
POST
/rulesets
Create a data-quality ruleset
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.
A
AWS Glue DataBrew
- AI-Aware (B-)61/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
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.
38
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AWS Glue DataBrew by hand means implementing AWS Signature v4 request signing, resolving the regional databrew host, and mapping dozens of dataset, project, recipe, and job operations to their REST paths yourself. Through Jentic you install once, import AWS Glue DataBrew from the API Directory, store the AWS credentials once, and your agent calls it.
Permission scoping
DataBrew names datasets, projects, recipes, and jobs in the request body when you create them rather than pinning them in the URL path. Limit the agent to the operations it needs, such as CreateRecipeJob and CreateSchedule, so operations like DeleteRecipe are not included unless you add them.
Credential isolation
Your AWS 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.
Intent-based discovery
Agents search Jentic by intent such as 'schedule a recurring data preparation job' or 'create a data-quality ruleset', and Jentic returns the matching AWS Glue DataBrew operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Glue DataBrew API through Jentic.
Why is there no official OpenAPI spec for AWS Glue DataBrew?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Glue DataBrew 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 AWS Glue DataBrew API use?
AWS Signature v4 (HMAC) with IAM permissions on databrew:* and pass-through permissions on the S3 buckets, Redshift clusters, or JDBC endpoints the dataset points to. Jentic stores the AWS credentials in its vault and signs each request.
Can I run a DataBrew recipe job programmatically?
Yes. Call CreateRecipeJob with the dataset, recipe reference, and output location, then StartJobRun. Track progress with DescribeJobRun and ListJobRuns; the run completes asynchronously.
What are the rate limits for the AWS Glue DataBrew API?
Per-account, per-region TPS limits apply, and there is a soft cap on concurrent job runs per account. StartJobRun and the Describe* operations are higher TPS than create operations.
How do I schedule a daily DataBrew job through Jentic?
Search Jentic for 'schedule a recurring DataBrew job', load the CreateSchedule schema, and execute it with a CronExpression and the JobNames to run. Schedules apply to one or more existing jobs.
What sources does AWS Glue DataBrew support?
DataBrew reads from Amazon S3 (CSV, JSON, Parquet, Excel), AWS Glue Data Catalog (S3, Redshift, JDBC), Snowflake (via JDBC), and Amazon Redshift directly. Outputs land in S3 in the chosen format.
Can I limit what my agent is allowed to do with the AWS Glue DataBrew API?
Yes. Because Jentic One is self-hosted, you decide which DataBrew operations your agent may call and which AWS credentials it uses. You can allow only the operations the agent needs, such as CreateRecipeJob and CreateSchedule, so write operations like DeleteRecipe are excluded unless you add them. DataBrew names datasets, projects, recipes, and jobs in the request body rather than the URL path, so scoping happens at the operation level under your own rules.
GET STARTED