AWS Amazon GuardDuty
Browse all Amazonaws APIs61
AI ReadinessAI-Aware (B-)61/100
Agent-ready OpenAPI document · curated by JenticSecurityThreat Detectionhmac67 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Investigate, archive, and act on Amazon GuardDuty findings and manage detectors, member accounts, threat intel sets, and malware scan plans across an AWS organisation.
Use for: I need to enable GuardDuty in a new region with all data sources turned on, List high-severity findings across the organisation in the last 7 days, Archive a finding once an analyst has confirmed it is a false positive, Add an IP CIDR to a trusted IP set so internal scanners stop triggering alerts
Not supported: Does not handle log ingestion, vulnerability scanning, or incident response automation - use for GuardDuty threat detection management and finding triage only.
Jentic publishes the only available OpenAPI specification for Amazon GuardDuty, keeping it validated and agent-ready. Amazon GuardDuty is a continuous threat detection service that analyses VPC flow logs, CloudTrail events, DNS logs, EKS audit logs, and EBS volume data to surface suspicious activity in AWS accounts. The API covers full lifecycle management of detectors, findings, threat intelligence sets, IP allow lists, member accounts, malware protection plans, and publishing destinations across 67 operations.
Install Jentic One Beta
Connect the Amazon GuardDuty to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon GuardDuty, 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%2Famazon-guardduty" | 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%2Famazon-guardduty" | 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 Amazon GuardDuty API.
Create and configure GuardDuty detectors with selected data sources and feature toggles
List and retrieve security findings with filtering by severity, type, and resource
Archive and unarchive findings to triage incidents at scale
Manage trusted IP sets and threat intel sets that suppress or escalate detections
Invite, accept, and manage GuardDuty member accounts under a single administrator
Configure malware protection scan plans for EC2 instances and EBS volumes
Publish findings to S3, EventBridge, or Security Hub via destinations and filters
Use Cases
Patterns agents use Amazon GuardDuty API for, with concrete tasks.
★ Centralised Multi-Account Threat Detection
Configure a delegated GuardDuty administrator account that aggregates findings from every member account in an AWS organisation. The API exposes EnableOrganizationAdminAccount, CreateMembers, InviteMembers, and ListMembers so an agent can onboard or audit accounts at scale. Findings flow into the administrator account where they can be filtered, archived, or republished.
Call EnableOrganizationAdminAccount for the security account, then CreateMembers with a list of AccountDetail entries and InviteMembers to send the invitation
Automated Finding Triage
Pull GuardDuty findings on a schedule, classify them by severity and type, archive low-severity false positives, and route the remainder to a SIEM or ticketing system. ListFindings supports rich filter criteria, GetFindings returns full detail for a batch, and ArchiveFindings closes off resolved cases. UpdateFindingsFeedback feeds analyst decisions back to AWS.
Call ListFindings with FindingCriteria filtering severity >= 7 and updatedAt within the last 24 hours, then GetFindings for the returned IDs
Custom Threat Intelligence Feeds
Add organisation-specific threat intelligence by uploading IOC lists to S3 and registering them as ThreatIntelSets. GuardDuty correlates incoming events against the lists and raises a CustomThreatIntel finding when a match occurs. The API also manages IPSets - trusted ranges that suppress noisy detections from known scanners or load balancers.
Call CreateThreatIntelSet with a Location pointing to an S3 object containing IOCs in TXT format, Activate=true, and a Format of TXT
AI Agent Security Operations
Through Jentic, an AI agent can act as an SOC analyst - paginating through findings, archiving false positives by pattern, updating IP allow lists, and triggering malware scans on suspicious EC2 instances. The 67 GuardDuty operations are exposed as Jentic tools so the agent picks the right one from intent.
Search Jentic for 'archive guardduty finding', load the ArchiveFindings schema, and execute it with the DetectorId and a list of FindingIds
Key Endpoints
67 endpoints — jentic publishes the only available openapi specification for amazon guardduty, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/detector
ListDetectors - list GuardDuty detectors in the region
GET
/detector/{detectorId}/filter
ListFilters - list saved finding filters
POST
/detector/{detectorId}/findings/archive
ArchiveFindings - archive a batch of findings
GET
/detector/{detectorId}/ipset
ListIPSets - list trusted IP sets on a detector
GET
/detector/{detectorId}/administrator
GetAdministratorAccount - fetch the admin account for the detector
GET
/detector
ListDetectors - list GuardDuty detectors in the region
GET
/detector/{detectorId}/filter
ListFilters - list saved finding filters
POST
/detector/{detectorId}/findings/archive
ArchiveFindings - archive a batch of findings
GET
/detector/{detectorId}/ipset
ListIPSets - list trusted IP sets on a detector
GET
/detector/{detectorId}/administrator
GetAdministratorAccount - fetch the admin account for the detector
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
Amazon GuardDuty
- AI-Aware (B-)61/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience91
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
95%
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
52%
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.
91
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
91%
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 Amazon GuardDuty by hand means building SigV4 request signing, resolving the GuardDuty host, and handling AWS throttling and retries yourself. Through Jentic you install once, import GuardDuty from the API Directory, store the AWS access keys once, and your agent calls it.
Permission scoping
GuardDuty puts the detector id in the URL path (/detector/{detectorId}/...), so a rule can pin your agent to one detector: it can read filters and IP sets and archive findings for that detector and nothing else. You choose the operations it may call, so deleting a detector or filter is not included unless you add it.
Credential isolation
Your AWS access keys for GuardDuty are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list GuardDuty findings' or 'archive a finding', and Jentic returns the matching GuardDuty operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon GuardDuty API through Jentic.
Why is there no official OpenAPI spec for Amazon GuardDuty?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon GuardDuty 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 Amazon GuardDuty API use?
The API uses AWS Signature Version 4 (HMAC) request signing. Through Jentic, AWS credentials are stored encrypted in the vault and requests are signed server-side, so the agent never holds raw access keys.
Can I list and filter GuardDuty findings with the API?
Yes. Call ListFindings on /detector/{detectorId}/findings with a FindingCriteria object that filters by severity, type, resource, or updatedAt. Pass the returned IDs to GetFindings to retrieve full finding details.
What are the rate limits for the Amazon GuardDuty API?
AWS applies per-account, per-region request quotas to GuardDuty operations and these vary by call. List operations have higher throughput than mutation operations like CreateDetector or InviteMembers. Check AWS Service Quotas for current limits.
How do I archive a finding through Jentic?
Search Jentic for 'archive guardduty finding', load the ArchiveFindings schema, and execute with the DetectorId and a list of up to 50 FindingIds. The archived findings remain queryable but no longer count as active.
Can I add custom threat intelligence to GuardDuty?
Yes. Upload an IOC list to S3 in TXT, STIX, OTX_CSV, ALIEN_VAULT, PROOF_POINT, or FIRE_EYE format and call CreateThreatIntelSet with the Location, Format, and Activate=true. GuardDuty raises a Custom finding type when an event matches an entry.
Can I limit what my agent is allowed to do with the Amazon GuardDuty API?
Yes. Because Jentic One is self-hosted, your own rules decide which GuardDuty operations and credentials the agent may use. Since GuardDuty carries the detector id in the URL path (/detector/{detectorId}/...), you can pin the agent to a single detector and allow only the calls you choose, such as reading filters and IP sets and archiving findings for that detector. Destructive operations like deleting a detector or filter stay off limits unless you explicitly add them.
GET STARTED