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 / Security / Google / Assured Workloads API
Assured Workloads API logo

Google Assured Workloads API

Browse all Google APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Official vendor OpenAPI document · agent-readySecurityComplianceoauth212 EndpointsREST

For Agents

Provision and govern Google Cloud Assured Workloads folders, restrict resource locations, acknowledge violations, and manage partner permissions for regulated workloads.

Use for: I need to create a FedRAMP High Assured Workloads folder for a federal customer, Restrict a workload to only allow Compute Engine and Cloud Storage resources, List all violations on a given Assured Workloads folder, Acknowledge a sovereignty violation that has been remediated

Not supported: Does not provision projects inside the workload, run application workloads, or remediate violations automatically - use for creating, configuring, and acknowledging posture on Assured Workloads folders only.

The Assured Workloads API programmatically manages Google Cloud's compliance-controlled folders that enforce regulatory regimes such as FedRAMP, IL4, CJIS, and EU Sovereign Controls on the resources created inside them. It exposes operations to create and update workloads, restrict allowed resource types and locations, mutate partner-controlled permissions, and acknowledge violations surfaced by the platform. Workload state changes are returned as long-running operations that callers must poll for completion. The API is the control-plane for compliance posture, not for building or running the underlying applications.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Assured Workloads API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Assured Workloads API, 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%2Fgoogleapis.com%2Fassuredworkloads" | 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%2Fgoogleapis.com%2Fassuredworkloads" | 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 Assured Workloads API.

Create a workload that enforces a chosen compliance regime such as FedRAMP_HIGH or EU_REGIONS_AND_SUPPORT

Restrict the set of allowed resource types within a workload via /v1/{+name}:restrictAllowedResources

Acknowledge a compliance violation surfaced on the workload to mark it reviewed

Enable resource monitoring on a workload via /v1/{+name}:enableResourceMonitoring

Mutate partner-controlled IAM permissions via /v1/{+name}:mutatePartnerPermissions for sovereign deployments

List long-running operations on a workload to track create and update progress

Use Cases

Patterns agents use Assured Workloads API for, with concrete tasks.

★ Provision a FedRAMP-Controlled Folder

Create a Google Cloud folder that automatically enforces FedRAMP High or Moderate controls on the projects placed inside it. The API returns a long-running operation while the workload is being prepared, then exposes endpoints to inspect violations and acknowledge them. Suited to regulated SaaS providers that need a repeatable, auditable provisioning path for compliant tenants.

POST a workload create request with complianceRegime=FEDRAMP_HIGH to /v1/{parent}/workloads and poll the returned operation until it completes.

Lock Down Allowed Resources for a Regulated Tenant

After a workload is created, restrict the resource types it can use to a curated allowlist so customers cannot inadvertently provision non-compliant services. The restrictAllowedResources endpoint accepts a list of allowed resource type strings and applies them at the workload boundary. Useful for tenants that must hold to a strict baseline like Compute Engine plus Cloud Storage only.

POST a list of allowed resource types to /v1/{name}:restrictAllowedResources for the workload and verify the response.

Acknowledge and Track Compliance Violations

When the platform raises a compliance violation on a workload, an operations team can list violations, investigate, and acknowledge each one through the API to record review. Acknowledgement does not remediate the underlying issue but records human review for audit purposes, fitting cleanly into a SOC workflow or ticketing integration.

POST an acknowledgement with the violation resource name to /v1/{name}:acknowledge and log the response in the SOC ticket.

Agent-Driven Compliance Posture Reviews via Jentic

Use an AI agent to run periodic posture reviews across an organisation's Assured Workloads, summarise open violations, and route them to the right owner. Through Jentic the agent discovers list and acknowledge operations by intent and executes them with org-scoped credentials supplied at call time, without managing service accounts inside the agent runtime.

Use Jentic search for 'list assured workloads in an organisation', iterate the results, and call the acknowledge endpoint for each violation marked closed in the ticketing system.

Key Endpoints

12 endpoints — the assured workloads api programmatically manages google cloud's compliance-controlled folders that enforce regulatory regimes such as fedramp, il4, cjis, and eu sovereign controls on the resources created inside them.

METHOD

PATH

DESCRIPTION

GET

/v1/{+name}

Get a workload or violation by resource name

PATCH

/v1/{+name}

Update a workload's mutable fields

DELETE

/v1/{+name}

Delete a workload

POST

/v1/{+name}:acknowledge

Acknowledge a compliance violation

POST

/v1/{+name}:restrictAllowedResources

Restrict the allowed resource types in a workload

POST

/v1/{+name}:enableResourceMonitoring

Enable resource monitoring on a workload

PATCH

/v1/{+name}:mutatePartnerPermissions

Update partner-controlled IAM permissions

GET

/v1/{+name}

Get a workload or violation by resource name

PATCH

/v1/{+name}

Update a workload's mutable fields

DELETE

/v1/{+name}

Delete a workload

POST

/v1/{+name}:acknowledge

Acknowledge a compliance violation

POST

/v1/{+name}:restrictAllowedResources

Restrict the allowed resource types in a workload

POST

/v1/{+name}:enableResourceMonitoring

Enable resource monitoring on a workload

PATCH

/v1/{+name}:mutatePartnerPermissions

Update partner-controlled IAM permissions

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

Assured Workloads API

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

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4
75%

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).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

18

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
74%

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.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

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

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

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 Assured Workloads API by hand means configuring Google OAuth2, granting a service account organization-scoped roles, and minting scoped access tokens for each compliance call yourself. Through Jentic you install once, import the Assured Workloads API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

This API puts the workload name in the URL path (/v1/{name}, /v1/{name}:acknowledge), so a rule can pin your agent to one workload: it can read the workload, acknowledge posture, and enable resource monitoring there and nothing else. You choose the operations it may call, so actions like deleting a workload are not included unless you add them.

Credential isolation

Your Google Cloud OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a FedRAMP workload' or 'acknowledge a violation', and Jentic returns the matching Assured Workloads operation with its input schema so the agent calls the right endpoint without walking Google's discovery document or compliance docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Resource Manager API

→

Creates the projects and folders that live inside an Assured Workload

Use alongside Assured Workloads to actually provision the projects under the compliance-bounded folder.

Complementary

Access Context Manager API

→

Defines access levels and service perimeters that complement workload boundaries

Pair when an agent needs to add VPC Service Controls perimeters around an Assured Workload.

Complementary

Security Command Center API

→

Surfaces broader security findings across the organisation including workload posture

Use to triage findings raised across many workloads, while Assured Workloads handles the regime-specific configuration.

FAQs

Specific to using Assured Workloads API through Jentic.

What authentication does the Assured Workloads API use?

The API uses Google OAuth 2.0 with cloud-platform scope. The caller must hold the assuredworkloads.workloads.* IAM permissions on the parent organisation or folder. Through Jentic the service account credential lives in the encrypted vault and the agent only sees short-lived access tokens.

Which compliance regimes can I enforce with the Assured Workloads API?

The workload create payload accepts a complianceRegime field; supported values include FedRAMP Moderate and High, IL4, CJIS, EU Regions and Support, EU Sovereign Controls, and Canada Controlled Goods Program among others. The exact set is documented on the workload create schema in the spec.

Are workload create and update operations synchronous?

No. Create, update, and delete return long-running operation handles. List the operations under the workload via GET /v1/{name}/operations and poll until done is true to confirm completion.

How do I acknowledge a compliance violation through Jentic?

Search Jentic for 'acknowledge an Assured Workloads violation', load the schema for POST /v1/{name}:acknowledge, and execute it with the violation resource name and an acknowledgement comment. The credential is supplied from your Jentic One instance.

What are the rate limits for the Assured Workloads API?

Numeric rate limits are not declared in the spec; quotas are enforced per project on assuredworkloads.googleapis.com. Review the project's quota settings in the Google Cloud console before bulk-creating workloads.

Can the API create the projects inside a workload?

No. Assured Workloads creates the bounded folder; projects inside it are still created via the Cloud Resource Manager API. Use the two together to fully provision a regulated tenant.

Can I limit what my agent is allowed to do with the Assured Workloads API?

Yes. Because this API carries the workload name in the URL path (/v1/{name}, /v1/{name}:acknowledge), your self-hosted Jentic One instance lets you write rules that pin the agent to a single workload and to a chosen set of operations, so it can read the workload, acknowledge violations, and enable resource monitoring there and nothing else. You decide which operations and credentials the agent may use, so destructive calls like deleting a workload or mutating partner permissions are excluded unless you add them. Your own rules, not the agent, determine what it can reach.

GET STARTED

Start building with Assured Workloads API

Explore with Jentic One
View OpenAPI Document