Amazon SimpleDB
Amazon SimpleDB is a highly available NoSQL data store that offloads the work of database administration. It provides simple and powerful data storage and querying capabilities to enable you to build web applications with structured data storage without the overhead of database administration.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon SimpleDB the way a machine reads it — 142 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon SimpleDB scores 67.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Amazon SimpleDB
Each block below is one kind of artifact we hold for Amazon SimpleDB. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon SimpleDB #Action=BatchDeleteAttributes API
The #Action=BatchDeleteAttributes API from Amazon SimpleDB — 1 operation(s) for #action=batchdeleteattributes.
Amazon SimpleDB #Action=BatchPutAttributes API
The #Action=BatchPutAttributes API from Amazon SimpleDB — 1 operation(s) for #action=batchputattributes.
Amazon SimpleDB #Action=CreateDomain API
The #Action=CreateDomain API from Amazon SimpleDB — 1 operation(s) for #action=createdomain.
Amazon SimpleDB #Action=DeleteAttributes API
The #Action=DeleteAttributes API from Amazon SimpleDB — 1 operation(s) for #action=deleteattributes.
Amazon SimpleDB #Action=DeleteDomain API
The #Action=DeleteDomain API from Amazon SimpleDB — 1 operation(s) for #action=deletedomain.
Amazon SimpleDB #Action=DomainMetadata API
The #Action=DomainMetadata API from Amazon SimpleDB — 1 operation(s) for #action=domainmetadata.
Amazon SimpleDB #Action=GetAttributes API
The #Action=GetAttributes API from Amazon SimpleDB — 1 operation(s) for #action=getattributes.
Amazon SimpleDB #Action=ListDomains API
The #Action=ListDomains API from Amazon SimpleDB — 1 operation(s) for #action=listdomains.
Amazon SimpleDB #Action=PutAttributes API
The #Action=PutAttributes API from Amazon SimpleDB — 1 operation(s) for #action=putattributes.
Amazon SimpleDB #Action=Select API
The #Action=Select API from Amazon SimpleDB — 1 operation(s) for #action=select.
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Simpledb Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Simpledb Finops
FINOPSFeatures 4
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Simple Data Storage
NoSQL data store with no database administration overhead.
Schema-less
Store structured data without a predefined schema.
High Availability
Automatically replicated data across multiple availability zones.
Select Query Language
Query data using a simple SELECT expression language.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Simpledb Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon SimpleDB API Rules
SPECTRALAmazon SimpleDB API Rules
SPECTRALJSON Schema 38
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AttributeDoesNotExist
JSON SCHEMAAttribute
JSON SCHEMABatchDeleteAttributesRequest
JSON SCHEMABatchPutAttributesRequest
JSON SCHEMACreateDomainRequest
JSON SCHEMADeletableAttribute
JSON SCHEMADeletableItem
JSON SCHEMADeleteAttributesRequest
JSON SCHEMADeleteDomainRequest
JSON SCHEMADomainMetadataRequest
JSON SCHEMADomainMetadataResult
JSON SCHEMADuplicateItemName
JSON SCHEMAGetAttributesRequest
JSON SCHEMAGetAttributesResult
JSON SCHEMAInvalidNextToken
JSON SCHEMAInvalidNumberPredicates
JSON SCHEMAInvalidNumberValueTests
JSON SCHEMAInvalidParameterValue
JSON SCHEMAInvalidQueryExpression
JSON SCHEMAItem
JSON SCHEMAListDomainsRequest
JSON SCHEMAListDomainsResult
JSON SCHEMAMissingParameter
JSON SCHEMANoSuchDomain
JSON SCHEMANumberDomainAttributesExceeded
JSON SCHEMANumberDomainBytesExceeded
JSON SCHEMANumberDomainsExceeded
JSON SCHEMANumberItemAttributesExceeded
JSON SCHEMANumberSubmittedAttributesExceeded
JSON SCHEMANumberSubmittedItemsExceeded
JSON SCHEMAPutAttributesRequest
JSON SCHEMAReplaceableAttribute
JSON SCHEMAReplaceableItem
JSON SCHEMARequestTimeout
JSON SCHEMASelectRequest
JSON SCHEMASelectResult
JSON SCHEMATooManyRequestedAttributes
JSON SCHEMAUpdateCondition
JSON SCHEMAScroll within the panel for all 38 ·
JSON Structure 38
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Simpledb Attribute Does Not Exist Structure
JSON STRUCTUREAmazon Simpledb Attribute Structure
JSON STRUCTUREAmazon Simpledb Batch Put Attributes Request Structure
JSON STRUCTUREAmazon Simpledb Create Domain Request Structure
JSON STRUCTUREAmazon Simpledb Deletable Attribute Structure
JSON STRUCTUREAmazon Simpledb Deletable Item Structure
JSON STRUCTUREAmazon Simpledb Delete Attributes Request Structure
JSON STRUCTUREAmazon Simpledb Delete Domain Request Structure
JSON STRUCTUREAmazon Simpledb Domain Metadata Request Structure
JSON STRUCTUREAmazon Simpledb Domain Metadata Result Structure
JSON STRUCTUREAmazon Simpledb Duplicate Item Name Structure
JSON STRUCTUREAmazon Simpledb Get Attributes Request Structure
JSON STRUCTUREAmazon Simpledb Get Attributes Result Structure
JSON STRUCTUREAmazon Simpledb Invalid Next Token Structure
JSON STRUCTUREAmazon Simpledb Invalid Number Predicates Structure
JSON STRUCTUREAmazon Simpledb Invalid Number Value Tests Structure
JSON STRUCTUREAmazon Simpledb Invalid Parameter Value Structure
JSON STRUCTUREAmazon Simpledb Invalid Query Expression Structure
JSON STRUCTUREAmazon Simpledb Item Structure
JSON STRUCTUREAmazon Simpledb List Domains Request Structure
JSON STRUCTUREAmazon Simpledb List Domains Result Structure
JSON STRUCTUREAmazon Simpledb Missing Parameter Structure
JSON STRUCTUREAmazon Simpledb No Such Domain Structure
JSON STRUCTUREAmazon Simpledb Number Domain Bytes Exceeded Structure
JSON STRUCTUREAmazon Simpledb Number Domains Exceeded Structure
JSON STRUCTUREAmazon Simpledb Put Attributes Request Structure
JSON STRUCTUREAmazon Simpledb Replaceable Attribute Structure
JSON STRUCTUREAmazon Simpledb Replaceable Item Structure
JSON STRUCTUREAmazon Simpledb Request Timeout Structure
JSON STRUCTUREAmazon Simpledb Select Request Structure
JSON STRUCTUREAmazon Simpledb Select Result Structure
JSON STRUCTUREAmazon Simpledb Too Many Requested Attributes Structure
JSON STRUCTUREAmazon Simpledb Update Condition Structure
JSON STRUCTUREScroll within the panel for all 38 ·
Examples 38
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Simpledb Item Example
EXAMPLEScroll within the panel for all 38 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 3
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Web Application Data Storage
Store and query structured data for web applications.
User Profile Storage
Store user attributes and preferences without schema management.
Metadata Storage
Store metadata for files, media, or other cloud resources.
Resources
Every other property we hold for Amazon SimpleDB — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-simpledb · machine-readable index on apis.io