Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Amazon Entity Resolution website screenshot

Amazon Entity Resolution

Amazon Entity Resolution is a service that helps you match and link related records across multiple applications, channels, and data stores using machine learning and configurable matching techniques to identify and consolidate records that refer to the same entity.

agent ready

Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.

Kin Score

API Evangelist profiles Amazon Entity Resolution the way a machine reads it — 269 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 Entity Resolution scores 75.8/100 (exemplar), 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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 75.8/100 · exemplar
Contract Quality 20.1 / 25
Developer Ergonomics 9.1 / 20
Commercial Clarity 17.9 / 20
Operational Transparency 8.2 / 13
Governance 10.4 / 12
Discoverability 10.0 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Amazon Entity Resolution

Each block below is one kind of artifact we hold for Amazon Entity Resolution. 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 Entity Resolution Matchingworkflows API

The Matchingworkflows API from Amazon Entity Resolution — 5 operation(s) for matchingworkflows.

Amazon Entity Resolution Schemas API

The Schemas API from Amazon Entity Resolution — 2 operation(s) for schemas.

Amazon Entity Resolution Tags API

The Tags API from Amazon Entity Resolution — 2 operation(s) for tags.

Postman Collections 1

A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.

Ready-to-run Postman collections for exercising this provider's APIs.

Open Collections 1

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

AWS EntityResolution

OPEN COLLECTION

Arazzo Workflows 6

Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.

Multi-step API workflows described with the Arazzo specification.

Amazon Entity Resolution Audit Latest Matching Job

List the jobs for a workflow and pull the full status and metrics of the most recent one.

ARAZZO

Amazon Entity Resolution Provision Matching Workflow

Register a schema mapping and create a matching workflow that references it.

ARAZZO

Amazon Entity Resolution Resolve Record Match ID

Confirm a processed workflow exists, then look up the Match ID for a single customer record.

ARAZZO

Amazon Entity Resolution Run Matching Pipeline

Stand up a schema mapping and matching workflow, start a job, and poll it to completion.

ARAZZO

Amazon Entity Resolution Start And Await Matching Job

Start a matching job on an existing workflow and poll until it reaches a terminal status.

ARAZZO

Amazon Entity Resolution Update And Rerun Matching Workflow

Update an existing matching workflow's configuration, then start a fresh job and poll it.

ARAZZO

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.

FinOps 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.

Features 5

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.

ML-Based Matching

Use machine learning models to match records across disparate datasets

Rule-Based Matching

Configure deterministic matching rules for exact and fuzzy matching

ID Mapping

Create and manage identity graphs linking records across data sources

Schema Mapping

Map input data schemas to standardized formats for consistent matching

Third-Party Data Providers

Enrich records with data from LiveRamp, Unified ID 2.0, and others

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 Entity Resolution Context

49 classes · 48 properties

JSON-LD

Spectral 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 Entity Resolution API Rules

5 rules · 3 warnings

SPECTRAL

Amazon Entity Resolution API Rules

25 rules · 10 errors · 13 warnings

SPECTRAL

JSON Schema 92

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.

AccessDeniedException

0 properties

JSON SCHEMA

AttributeMatchingModel

0 properties

JSON SCHEMA

AttributeName

0 properties

JSON SCHEMA

Boolean

0 properties

JSON SCHEMA

ConflictException

0 properties

JSON SCHEMA

CreateMatchingWorkflowInput

8 properties

JSON SCHEMA

CreateMatchingWorkflowOutput

8 properties

JSON SCHEMA

CreateSchemaMappingInput

4 properties

JSON SCHEMA

CreateSchemaMappingOutput

4 properties

JSON SCHEMA

DeleteMatchingWorkflowInput

0 properties

JSON SCHEMA

DeleteMatchingWorkflowOutput

1 properties

JSON SCHEMA

DeleteSchemaMappingInput

0 properties

JSON SCHEMA

DeleteSchemaMappingOutput

1 properties

JSON SCHEMA

Description

0 properties

JSON SCHEMA

EntityName

0 properties

JSON SCHEMA

ErrorDetails

1 properties

JSON SCHEMA

ExceedsLimitException

0 properties

JSON SCHEMA

GetMatchIdInput

1 properties

JSON SCHEMA

GetMatchIdOutput

1 properties

JSON SCHEMA

GetMatchingJobInput

0 properties

JSON SCHEMA

GetMatchingJobOutput

6 properties

JSON SCHEMA

GetMatchingWorkflowInput

0 properties

JSON SCHEMA

GetMatchingWorkflowOutput

11 properties

JSON SCHEMA

GetSchemaMappingInput

0 properties

JSON SCHEMA

GetSchemaMappingOutput

7 properties

JSON SCHEMA

IncrementalRunConfig

1 properties

JSON SCHEMA

IncrementalRunType

0 properties

JSON SCHEMA

InputSourceConfig

0 properties

JSON SCHEMA

InputSourceInputSourceARNString

0 properties

JSON SCHEMA

InputSource

3 properties

JSON SCHEMA

Integer

0 properties

JSON SCHEMA

InternalServerException

0 properties

JSON SCHEMA

JobId

0 properties

JSON SCHEMA

JobList

0 properties

JSON SCHEMA

JobMetrics

4 properties

JSON SCHEMA

JobStatus

0 properties

JSON SCHEMA

JobSummary

4 properties

JSON SCHEMA

KMSArn

0 properties

JSON SCHEMA

ListMatchingJobsInput

0 properties

JSON SCHEMA

ListMatchingJobsOutput

2 properties

JSON SCHEMA

ListMatchingWorkflowsInput

0 properties

JSON SCHEMA

ListMatchingWorkflowsOutput

2 properties

JSON SCHEMA

ListSchemaMappingsInput

0 properties

JSON SCHEMA

ListSchemaMappingsOutput

2 properties

JSON SCHEMA

ListTagsForResourceInput

0 properties

JSON SCHEMA

ListTagsForResourceOutput

1 properties

JSON SCHEMA

MatchingWorkflowArn

0 properties

JSON SCHEMA

MatchingWorkflowList

0 properties

JSON SCHEMA

MatchingWorkflowSummary

4 properties

JSON SCHEMA

NextToken

0 properties

JSON SCHEMA

OutputAttribute

2 properties

JSON SCHEMA

OutputSourceConfig

0 properties

JSON SCHEMA

OutputSourceOutputList

0 properties

JSON SCHEMA

OutputSourceOutputS3PathString

0 properties

JSON SCHEMA

OutputSource

4 properties

JSON SCHEMA

RecordAttributeMapKeyString

0 properties

JSON SCHEMA

RecordAttributeMap

0 properties

JSON SCHEMA

RecordAttributeMapValueString

0 properties

JSON SCHEMA

ResolutionTechniques

2 properties

JSON SCHEMA

ResolutionType

0 properties

JSON SCHEMA

ResourceNotFoundException

0 properties

JSON SCHEMA

RuleBasedPropertiesRulesList

0 properties

JSON SCHEMA

RuleBasedProperties

2 properties

JSON SCHEMA

RuleMatchingKeysList

0 properties

JSON SCHEMA

RuleRuleNameString

0 properties

JSON SCHEMA

Rule

2 properties

JSON SCHEMA

SchemaAttributeType

0 properties

JSON SCHEMA

SchemaInputAttribute

4 properties

JSON SCHEMA

SchemaInputAttributes

0 properties

JSON SCHEMA

SchemaMappingArn

0 properties

JSON SCHEMA

SchemaMappingList

0 properties

JSON SCHEMA

SchemaMappingSummary

4 properties

JSON SCHEMA

StartMatchingJobInput

0 properties

JSON SCHEMA

StartMatchingJobOutput

1 properties

JSON SCHEMA

String

0 properties

JSON SCHEMA

TagKeyList

0 properties

JSON SCHEMA

TagKey

0 properties

JSON SCHEMA

TagMap

0 properties

JSON SCHEMA

TagResourceInput

1 properties

JSON SCHEMA

TagResourceOutput

0 properties

JSON SCHEMA

TagValue

0 properties

JSON SCHEMA

ThrottlingException

0 properties

JSON SCHEMA

Timestamp

0 properties

JSON SCHEMA

UntagResourceInput

0 properties

JSON SCHEMA

UntagResourceOutput

0 properties

JSON SCHEMA

UpdateMatchingWorkflowInput

6 properties

JSON SCHEMA

UpdateMatchingWorkflowOutput

7 properties

JSON SCHEMA

ValidationException

0 properties

JSON SCHEMA

VeniceGlobalArn

0 properties

JSON SCHEMA

Scroll within the panel for all 92 ·

JSON Structure 92

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 Entity Resolution Boolean Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Integer Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Job Id Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Kms Arn Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Rule Structure

2 properties

JSON STRUCTURE

Amazon Entity Resolution String Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Tag Key Structure

0 properties

JSON STRUCTURE

Amazon Entity Resolution Tag Map Structure

0 properties

JSON STRUCTURE

Scroll within the panel for all 92 ·

Examples 54

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 54 ·

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.

Amazon Entity Resolution Authentication

apiKey · 1 scheme

SECURITY

Amazon Entity Resolution Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Amazon Entity Resolution Vulnerability Disclosure

security.txt · contact published

SECURITY

Amazon Entity Resolution Trust Center

PCI DSS, HIPAA, FedRAMP, GDPR, FIPS 140

SECURITY

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.

Amazon Entity Resolution Agentic Access

16 operations · 9 acting

16 operations · 9 acting

AGENTIC

Use Cases 4

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.

Customer Data Unification

Create a single customer view by matching records across CRM, marketing, and transaction systems

Data Deduplication

Identify and remove duplicate records from databases and data lakes

Identity Resolution for Advertising

Link user identities across devices and channels for targeted advertising

Healthcare Record Matching

Match patient records across different healthcare providers and systems

Resources

Every other property we hold for Amazon Entity Resolution — 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.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Scroll within the panel for all 8 ·

Build 2

SDKs, sample code, and the tooling you integrate with

Learn 1

Tutorials, courses, talks, and written guidance

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/amazon-entity-resolution · machine-readable index on apis.io