AWS Service Catalog App Registry
Browse all Amazonaws APIs62
AI ReadinessAI-Aware (B-)62/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeapiKey24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Catalogue applications, attach metadata attribute groups, and bind AWS resources to applications in App Registry. Agents can register applications and discover all resources tied to a given application.
Use for: I need to register a new application in App Registry, Attach a metadata attribute group to an existing application, Associate a CloudFormation stack with an App Registry application, List all resources currently associated with an application
Not supported: Does not provision resources, manage IaC templates, or share resources across accounts - use for cataloguing applications and attaching metadata only.
Jentic publishes the only available OpenAPI specification for AWS Service Catalog App Registry, keeping it validated and agent-ready. App Registry gives organisations a structured repository of their applications, the AWS resources that compose them, and the metadata needed to operate and govern them. Agents can create applications, attach attribute groups that carry custom JSON schemas, associate or disassociate AWS resources, and query the resulting application graph. The 24 operations cover applications, attribute groups, resource associations, sync, and tag management.
Install Jentic One Beta
Connect the AWS Service Catalog App Registry to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Service Catalog App Registry, 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-service-catalog-appregistry" | 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-service-catalog-appregistry" | 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 Service Catalog App Registry API.
Register applications in App Registry with CreateApplication and update them via UpdateApplication
Attach reusable JSON metadata via attribute groups using CreateAttributeGroup and AssociateAttributeGroup
Bind AWS resources (CloudFormation stacks, resource groups) to an application with AssociateResource
Query an application's associated resources, attribute groups, and tags with ListAssociated* operations
Sync resource state into App Registry on demand with SyncResource
Tag and untag applications and attribute groups for billing and governance
Use Cases
Patterns agents use AWS Service Catalog App Registry API for, with concrete tasks.
★ Application Inventory for a Multi-Service System
Platform teams use App Registry to declare each business application as a first-class entity, then attach the CloudFormation stacks, EC2 instances, and other resources that implement it. Once associated, ListAssociatedResources gives a complete view of which AWS resources belong to which application - useful for cost allocation, change management, and runbooks.
CreateApplication named 'checkout-service', then AssociateResource to bind two CloudFormation stack ARNs to it, and call ListAssociatedResources to verify.
Standardised Application Metadata via Attribute Groups
Governance teams define attribute groups that capture required metadata (tier, owner, data classification, compliance scope) and attach them to many applications. Because attribute groups carry a JSON schema, downstream automation can rely on the shape of the data without per-team variation.
CreateAttributeGroup with a JSON schema for {tier, owner, compliance}, then AssociateAttributeGroup to bind it to applications 'checkout-service' and 'orders-service'.
Resource Reconciliation Across CloudFormation Updates
When CloudFormation stacks change, App Registry can be kept in sync so that the application's resource list reflects reality. SyncResource refreshes the latest state for a specific associated resource, and ListAssociatedResources reveals drift between declared and actual membership.
Call SyncResource for resourceType=CFN_STACK and resource=<stack-arn> on application 'orders-service', then ListAssociatedResources to confirm the refreshed status.
AI Agent Application Discovery via Jentic
AI agents using Jentic can answer questions like 'which resources belong to the checkout application?' by calling App Registry through Jentic. The agent searches by intent, loads the operation schema, and executes List operations against the agent's AWS credentials in the vault.
Search Jentic for 'list resources associated with an appregistry application', execute GetApplication for 'checkout-service', then call the associated-resources listing to return the bound CloudFormation stacks.
Key Endpoints
24 endpoints — jentic publishes the only available openapi specification for aws service catalog app registry, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/applications
Create an App Registry application
GET
/applications
List all applications in the account
PATCH
/applications/{application}
Update an application's name or description
PUT
/applications/{application}/attribute-groups/{attributeGroup}
Attach an attribute group to an application
PUT
/applications/{application}/resources/{resourceType}/{resource}
Associate an AWS resource with an application
GET
/applications/{application}/resources/{resourceType}/{resource}
Get details for an associated resource
POST
/attribute-groups
Create a reusable attribute group
POST
/applications
Create an App Registry application
GET
/applications
List all applications in the account
PATCH
/applications/{application}
Update an application's name or description
PUT
/applications/{application}/attribute-groups/{attributeGroup}
Attach an attribute group to an application
PUT
/applications/{application}/resources/{resourceType}/{resource}
Associate an AWS resource with an application
GET
/applications/{application}/resources/{resourceType}/{resource}
Get details for an associated resource
POST
/attribute-groups
Create a reusable attribute group
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 Service Catalog App Registry
- AI-Aware (B-)62/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility39
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
97%
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.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
54%
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 Service Catalog App Registry by hand means implementing AWS SigV4 signing, resolving the servicecatalog-appregistry regional host, and mapping resource types like CFN_STACK into the association path yourself. Through Jentic you install once, import AWS Service Catalog App Registry from the API Directory, store your AWS access key and secret once, and your agent calls it.
Permission scoping
App Registry puts the application identifier in the URL path (/applications/{application}/resources/{resourceType}/{resource}), so a rule can pin your agent to one application: it can read and list the resources bound to that application and nothing else. You choose the operations it may call, so DeleteApplication or DisassociateResource are not included unless you add them.
Credential isolation
Your AWS access key and secret are stored once, encrypted, by your own Jentic One instance and each request is signed with SigV4 at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register an application in App Registry' or 'list resources associated with an application', and Jentic returns the matching operation like CreateApplication or GetAssociatedResource with its input schema so the agent calls it without reading the AWS reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Service Catalog App Registry API through Jentic.
Why is there no official OpenAPI spec for AWS Service Catalog App Registry?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Service Catalog App Registry 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 Service Catalog App Registry use?
App Registry uses AWS Signature Version 4 with IAM credentials and permissions on the servicecatalog:* and resource-groups:* actions. Through Jentic, the AWS access key and secret are stored encrypted in the vault and signed into each request - agents never see the raw credentials.
Can I associate any AWS resource with an App Registry application?
App Registry supports specific resource types - CloudFormation stacks (CFN_STACK) and AWS Resource Groups (RESOURCE_TAG_VALUE) - bound via AssociateResource at /applications/{application}/resources/{resourceType}/{resource}. Other AWS services are tracked indirectly through the CloudFormation stacks that create them.
What are the rate limits for the AWS Service Catalog App Registry?
App Registry uses standard AWS API throttling - most operations are limited to roughly 5-10 requests per second per account per region with brief burst capacity. Throttled requests return a ThrottlingException; clients should retry with exponential backoff.
How do I list every resource bound to an application through Jentic?
Through Jentic, search for 'list associated resources appregistry', load the operation schema, and execute against /applications/{application} with the application name. Jentic returns the resource list along with each association's lastSyncTime.
Is AWS Service Catalog App Registry free?
App Registry itself is offered at no additional charge - you pay only for the underlying resources you catalogue. Standard AWS Service Catalog product pricing applies if you also use Service Catalog provisioned products.
Can I limit what my agent is allowed to do with the AWS Service Catalog App Registry API?
Yes. Because you run Jentic One yourself, your own rules decide which App Registry operations and AWS credentials the agent may use. App Registry puts the application identifier in the URL path (/applications/{application}/resources/{resourceType}/{resource}), so you can pin the agent to a single application and let it only read and list the resources and attribute groups bound to that application. You choose the operations it may call, so write actions like DeleteApplication or DisassociateResource are excluded unless you explicitly add them.
GET STARTED