Aura Historia
Aura Historia is a global platform for antiques, art, and distinctive objects. It indexes dealers, auction houses, and specialist sellers worldwide, providing a single searchable view for collectors, decorators, and trade professionals. The service aggregates scattered inventory, offers watchlists, alerts, and multilingual search, and connects users directly to original listings, ensuring clarity and accessibility across markets.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Aura Historia the way a machine reads it — 37 machine-readable artifacts across 2 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 — Aura Historia scores 43.3/100 (developing), with a separate agent-readiness read of 51/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Aura Historia's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aura-historia-com/"
title="Aura Historia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aura-historia-com.svg"
alt="Aura Historia Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/aura-historia-com/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aura-historia-com/"
title="Aura Historia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aura-historia-com/card.svg"
alt="Aura Historia Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Aura Historia
Each block below is one kind of artifact we hold for Aura Historia. 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 18
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.
Aura Historia Administration API
The Administration API from Aura Historia — 1 operation(s) for administration.
Aura Historia Auctions API
Public Auction discovery, catalogue reads, and administrator Auction management.
Aura Historia Billing API
Stripe checkout, billing-portal, and subscription-management session creation for authenticated users.
Aura Historia Listing Sources API
ListingSource retrieval, authenticated creation and update, and caller-administered listing sources.
Aura Historia Newsletter API
Newsletter subscription upsert workflows for website or product-surface sign-up flows.
Aura Historia Notifications API
In-app notification retrieval, bulk updates, single-notification updates, and notification cleanup workflows.
Aura Historia OAuth API
OAuth 2.0 authorization, token, revocation, introspection, and OAuth client metadata management.
Aura Historia Operations API
Public process liveness and service readiness probes.
Aura Historia Overview API
Public aggregate catalogue statistics.
Aura Historia Parties API
The Parties API from Aura Historia — 1 operation(s) for parties.
Aura Historia Partnership Applications API
Partnership application submission, review tracking, administration, and decision workflows.
Aura Historia Partnerships API
Partnership administration, safe summary reads, and membership/ListingSource count workflows.
Aura Historia Party API
The Party API from Aura Historia — 7 operation(s) for party.
Aura Historia Product Listings API
Product retrieval, product history, similar-product discovery, product search, and partner catalog ingestion workflows.
Aura Historia Search Filters API
Saved search creation, maintenance, persisted matches, and match-feedback workflows.
Aura Historia User Account API
Authenticated user profile management, admin user management, access-token lifecycle management, and partnership listing.
Aura Historia Users API
The Users API from Aura Historia — 3 operation(s) for users.
Aura Historia Watchlist API
Watchlist membership, notification preferences, and watchlist-specific product state for authenticated users.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Agent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
discover-party-locations
AGENT SKILLSemantic 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.
Aura Historia Com Context
JSON-LDSpectral Rules 1
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.
Aura Historia API Rules
SPECTRALJSON Schema 11
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.
AsyncProductListingBatchReport
JSON SCHEMACreateProductListingData
JSON SCHEMAOAuthClientConsentMetadataData
JSON SCHEMAOAuthClientMetadataResponseData
JSON SCHEMAOAuthTokenResponseData
JSON SCHEMAReplaceShippingProfileData
JSON SCHEMAShippingDefaultData
JSON SCHEMAShippingProfileData
JSON SCHEMAUpdateProductListingData
JSON SCHEMAUpsertProductListingData
JSON SCHEMAWoocommerceProductWebhookUpsertData
JSON SCHEMAScroll within the panel for all 11 ·
Security Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Aura Historia — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aura-historia-com · machine-readable index on apis.io
This is an independent, third-party profile of Aura Historia, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.