Amazon QLDB
Amazon Quantum Ledger Database (QLDB) is a fully managed ledger database that provides a transparent, immutable, and cryptographically verifiable transaction log. QLDB tracks each and every application data change and maintains a complete and verifiable history of changes over time, making it ideal for systems of record where data integrity and auditability are critical.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon QLDB the way a machine reads it — 129 machine-readable artifacts across 3 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 QLDB scores 64.7/100 (strong), with a separate agent-readiness read of 55/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon QLDB
Each block below is one kind of artifact we hold for Amazon QLDB. 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 3
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 QLDB Journal S3 Exports API
The Journal S3 Exports API from Amazon QLDB — 1 operation(s) for journal s3 exports.
Amazon QLDB Ledgers API
The Ledgers API from Amazon QLDB — 10 operation(s) for ledgers.
Amazon QLDB Tags API
The Tags API from Amazon QLDB — 2 operation(s) for tags.
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 Qldb 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 Qldb Finops
FINOPSSemantic 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 Qldb 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 QLDB API Rules
SPECTRALAmazon QLDB API Rules
SPECTRALJSON Schema 41
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.
CancelJournalKinesisStreamResponse
JSON SCHEMACreateLedgerRequest
JSON SCHEMACreateLedgerResponse
JSON SCHEMADescribeJournalKinesisStreamResponse
JSON SCHEMADescribeJournalS3ExportResponse
JSON SCHEMADescribeLedgerResponse
JSON SCHEMAEncryptionStatus
JSON SCHEMAErrorCause
JSON SCHEMAExportJournalToS3Request
JSON SCHEMAExportJournalToS3Response
JSON SCHEMAExportStatus
JSON SCHEMAGetBlockRequest
JSON SCHEMAGetBlockResponse
JSON SCHEMAGetDigestResponse
JSON SCHEMAGetRevisionRequest
JSON SCHEMAGetRevisionResponse
JSON SCHEMAJournalKinesisStreamDescription
JSON SCHEMAJournalS3ExportDescription
JSON SCHEMAKinesisConfiguration
JSON SCHEMALedgerEncryptionDescription
JSON SCHEMALedgerState
JSON SCHEMALedgerSummary
JSON SCHEMAListJournalKinesisStreamsForLedgerResponse
JSON SCHEMAListJournalS3ExportsForLedgerResponse
JSON SCHEMAListJournalS3ExportsResponse
JSON SCHEMAListLedgersResponse
JSON SCHEMAListTagsForResourceResponse
JSON SCHEMAOutputFormat
JSON SCHEMAPermissionsMode
JSON SCHEMAS3EncryptionConfiguration
JSON SCHEMAS3ExportConfiguration
JSON SCHEMAS3ObjectEncryptionType
JSON SCHEMAStreamJournalToKinesisRequest
JSON SCHEMAStreamJournalToKinesisResponse
JSON SCHEMAStreamStatus
JSON SCHEMATagResourceRequest
JSON SCHEMAUpdateLedgerPermissionsModeRequest
JSON SCHEMAUpdateLedgerPermissionsModeResponse
JSON SCHEMAUpdateLedgerRequest
JSON SCHEMAUpdateLedgerResponse
JSON SCHEMAValueHolder
JSON SCHEMAScroll within the panel for all 41 ·
JSON Structure 41
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 Qldb Create Ledger Request Structure
JSON STRUCTUREAmazon Qldb Create Ledger Response Structure
JSON STRUCTUREAmazon Qldb Describe Journal S3Export Response Structure
JSON STRUCTUREAmazon Qldb Describe Ledger Response Structure
JSON STRUCTUREAmazon Qldb Encryption Status Structure
JSON STRUCTUREAmazon Qldb Error Cause Structure
JSON STRUCTUREAmazon Qldb Export Journal To S3Request Structure
JSON STRUCTUREAmazon Qldb Export Journal To S3Response Structure
JSON STRUCTUREAmazon Qldb Export Status Structure
JSON STRUCTUREAmazon Qldb Get Block Request Structure
JSON STRUCTUREAmazon Qldb Get Block Response Structure
JSON STRUCTUREAmazon Qldb Get Digest Response Structure
JSON STRUCTUREAmazon Qldb Get Revision Request Structure
JSON STRUCTUREAmazon Qldb Get Revision Response Structure
JSON STRUCTUREAmazon Qldb Journal Kinesis Stream Description Structure
JSON STRUCTUREAmazon Qldb Journal S3Export Description Structure
JSON STRUCTUREAmazon Qldb Kinesis Configuration Structure
JSON STRUCTUREAmazon Qldb Ledger Encryption Description Structure
JSON STRUCTUREAmazon Qldb Ledger State Structure
JSON STRUCTUREAmazon Qldb Ledger Summary Structure
JSON STRUCTUREAmazon Qldb List Journal S3Exports Response Structure
JSON STRUCTUREAmazon Qldb List Ledgers Response Structure
JSON STRUCTUREAmazon Qldb List Tags For Resource Response Structure
JSON STRUCTUREAmazon Qldb Output Format Structure
JSON STRUCTUREAmazon Qldb Permissions Mode Structure
JSON STRUCTUREAmazon Qldb S3Encryption Configuration Structure
JSON STRUCTUREAmazon Qldb S3Export Configuration Structure
JSON STRUCTUREAmazon Qldb S3Object Encryption Type Structure
JSON STRUCTUREAmazon Qldb Stream Journal To Kinesis Request Structure
JSON STRUCTUREAmazon Qldb Stream Journal To Kinesis Response Structure
JSON STRUCTUREAmazon Qldb Stream Status Structure
JSON STRUCTUREAmazon Qldb Tag Resource Request Structure
JSON STRUCTUREAmazon Qldb Update Ledger Request Structure
JSON STRUCTUREAmazon Qldb Update Ledger Response Structure
JSON STRUCTUREAmazon Qldb Value Holder Structure
JSON STRUCTUREScroll within the panel for all 41 ·
Examples 33
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.
Scroll within the panel for all 33 ·
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.
Resources
Every other property we hold for Amazon QLDB — 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 42
Reference material describing how the API behaves
Scroll within the panel for all 42 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 43
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 43 ·
Build 34
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 34 ·
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-qldb · machine-readable index on apis.io