Agent-ready OpenAPI document · curated by JenticCloud InfrastructureServerlesshmac66 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Deploy, configure, and invoke serverless functions, manage event source mappings, and control concurrency, versions, and aliases on AWS.
Use for: I need to deploy a new Lambda function, Invoke a function with a custom payload, Get the configuration of a function, Publish a new version of a function
Not supported: Does not handle long-running container workloads, persistent VMs, or container image registry operations - use for serverless function lifecycle, invocation, and event source management only.
Jentic publishes the only available OpenAPI specification for AWS Lambda, keeping it validated and agent-ready. Lambda is the AWS serverless compute service that runs code in response to events without provisioning servers. The 66-endpoint API covers function lifecycle, alias and version management, layers, event source mappings to SQS, Kinesis, and DynamoDB, function URLs, code signing configurations, concurrency controls, and synchronous and asynchronous invocations. It is the foundation of most event-driven AWS architectures and pairs with API Gateway, EventBridge, and S3 for end-to-end serverless applications.
Install Jentic One Beta
Connect the AWS Lambda to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Lambda, 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%2Flambda" | 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%2Flambda" | 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 Lambda API.
Create and update Lambda functions via /2015-03-31/functions
Invoke functions synchronously or asynchronously through /2015-03-31/functions/{FunctionName}/invocations
Publish versions and manage weighted aliases for blue/green deployments
Wire SQS, Kinesis, DynamoDB Streams, and Kafka triggers via event source mappings
Configure function URLs for direct HTTPS invocation without API Gateway
Manage layers for shared code dependencies
Set reserved and provisioned concurrency to control scaling and cost
Use Cases
Patterns agents use AWS Lambda API for, with concrete tasks.
★ Event-Driven Backend Processing
Process events from S3, SQS, EventBridge, DynamoDB Streams, and Kafka with serverless Lambda functions. The Lambda API creates functions with a chosen runtime, attaches event source mappings that handle batching and retries automatically, and exposes concurrency controls so a runaway producer cannot consume the account quota. Engineers ship business logic as a zip or container image without managing instances.
Create a function 'order-processor' with runtime python3.12 and an SQS event source mapping reading from queue arn:aws:sqs:us-east-1:123:orders
Blue/Green Deploys with Aliases
Roll out new function code safely by publishing immutable versions and shifting traffic via aliases. The Lambda API supports weighted aliases that split traffic between two versions, enabling canary and linear deployments without external orchestration. Combined with CodeDeploy, alias updates can pause and roll back automatically based on alarms.
Update alias 'live' on function order-processor to send 10 percent of traffic to version 7 and 90 percent to version 6
Function URLs for Direct HTTPS
Expose a Lambda function over HTTPS without standing up API Gateway. POST /2021-10-31/functions/{FunctionName}/url creates a dedicated URL with optional IAM auth, CORS, and an invoke mode for response streaming. This is the simplest path to a serverless HTTPS endpoint for webhooks, internal tools, or LLM agent backends.
Create a function URL on function 'webhook-receiver' with AWS_IAM auth and CORS allowing origin https://example.com
AI Agent Serverless Operations
AI agents call Lambda through Jentic to invoke business-logic functions on demand, deploy new functions when teams onboard new workflows, and adjust concurrency in response to alerts. Through Jentic, the agent searches by intent, loads the operation schema, and executes with credentials kept in the vault. SigV4 signing happens inside Jentic so the agent runtime stays simple.
Search Jentic for 'invoke lambda function', load the Invoke schema, and call function 'order-processor' with payload {"orderId": "abc"}
Key Endpoints
66 endpoints — jentic publishes the only available openapi specification for aws lambda, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/2015-03-31/functions
Create a Lambda function
GET
/2015-03-31/functions
List functions
POST
/2015-03-31/functions/{FunctionName}/aliases
Create an alias
POST
/2015-03-31/event-source-mappings/
Create an event source mapping
POST
/2021-10-31/functions/{FunctionName}/url
Create a function URL
POST
/2018-10-31/layers/{LayerName}/versions
Publish a new layer version
POST
/2015-03-31/functions
Create a Lambda function
GET
/2015-03-31/functions
List functions
POST
/2015-03-31/functions/{FunctionName}/aliases
Create an alias
POST
/2015-03-31/event-source-mappings/
Create an event source mapping
POST
/2021-10-31/functions/{FunctionName}/url
Create a function URL
POST
/2018-10-31/layers/{LayerName}/versions
Publish a new layer version
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 Lambda
- Foundational (C+)60/100
73
Foundational Compliance63
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience92
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
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).
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.
51%
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
56%
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.
92
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
92%
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 the AWS Lambda API by hand means building AWS Signature Version 4 signing, selecting the right regional host from lambda.{region}.amazonaws.com, wiring IAM roles and event source mappings, and handling AWS throttling and retries yourself. Through Jentic you install once, import AWS Lambda from the API Directory, store the AWS access key and secret once, and your agent calls it.
Permission scoping
Lambda puts the function name in the URL path (/2015-03-31/functions/{FunctionName}/...), so a rule can pin your agent to one function: it can invoke and read the configuration of that function and nothing else. You choose the operations it may call, so destructive ones like DeleteFunction or removing an event source mapping are not included unless you add them.
Credential isolation
Your AWS access key and secret for Lambda are stored once, encrypted, by your own Jentic One instance and 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 'invoke a lambda function with a payload' or 'create a lambda event source mapping', and Jentic returns the matching Lambda operation with its input schema so the agent calls the right endpoint without reading the AWS reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Lambda API through Jentic.
Why is there no official OpenAPI spec for AWS Lambda?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Lambda 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 Lambda API use?
AWS Lambda uses AWS Signature Version 4 (SigV4) HMAC request signing scoped to the Lambda IAM service. Function URLs additionally support AWS_IAM or NONE authorization for direct HTTPS invocations. Through Jentic, AWS credentials live in the encrypted vault and SigV4 signing happens at execution time.
Can I invoke a Lambda function with the AWS Lambda API?
Yes. Use the Invoke endpoint at POST /2015-03-31/functions/{FunctionName}/invocations with InvocationType set to RequestResponse for synchronous calls, Event for fire-and-forget, or DryRun to validate permissions without executing.
How do I deploy a new Lambda function through Jentic?
Search Jentic for 'create lambda function', load the schema for POST /2015-03-31/functions, supply the runtime, role ARN, handler, and either a zip code reference or container image URI, then call the same operation with PUT semantics to update code in future. Jentic handles SigV4 signing throughout.
What are the rate limits for the AWS Lambda API?
Per-region quotas apply, including default concurrent execution limits, function and layer counts, and TPS limits on control plane operations. The Invoke API itself is bounded by reserved or provisioned concurrency on the function. Check the Lambda service quotas in the AWS console for current values.
Can I expose a Lambda function over HTTPS without API Gateway?
Yes. POST /2021-10-31/functions/{FunctionName}/url creates a dedicated function URL with optional IAM authorization, CORS configuration, and BUFFERED or RESPONSE_STREAM invoke mode for streaming responses.
Can I run a canary deployment with Lambda aliases?
Yes. Publish a new version with PublishVersion, then update an alias with a routing configuration that points a percentage of traffic to the new version. Combine with CloudWatch alarms and CodeDeploy for automated rollback.
Can I limit what my agent is allowed to do with the AWS Lambda API?
Yes. Because you run Jentic One yourself, your own rules decide which Lambda operations and which AWS credentials the agent may use. Since Lambda puts the function name in the URL path (/2015-03-31/functions/{FunctionName}/...), a rule can pin the agent to a single function so it only invokes and reads the configuration of that function and nothing else. Destructive operations such as DeleteFunction or removing an event source mapping are excluded unless you explicitly add them to the agent's allowed set.
GET STARTED