Aisle
Aisle provides a destination wedding venue marketplace and website builder, enabling couples to discover venues worldwide, estimate costs, and manage planning through an integrated platform. Users can browse venues, create wedding websites, collect RSVPs, and handle payments, with features like budgeting tools, checklists, and timeline planning. The service also offers AI assistance via ChatGPT and supports planners with customizable tools and real‑wedding showcases.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Aisle the way a machine reads it — 31 machine-readable artifacts across 1 API, 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 — Aisle scores 38.5/100 (thin), with a separate agent-readiness read of 46/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. 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 Aisle'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/aisle-wedding/"
title="Aisle on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aisle-wedding.svg"
alt="Aisle Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/aisle-wedding/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aisle-wedding/"
title="Aisle on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aisle-wedding/card.svg"
alt="Aisle 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 Aisle
Each block below is one kind of artifact we hold for Aisle. 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.
Aisle Dress codes API
Reusable event dress guidance.
Aisle Events API
Wedding schedule and invitations.
Aisle Guest access API
Individual and group invitation codes for custom frontends. Access grants name explicit guests and never change RSVP Parties. All operations require a server-side wedding API ke...
Aisle Guest content API
Guestbook notes, song requests, and predictions.
Aisle Guests API
Manage the wedding guest list and room assignments.
Aisle Media API
Wedding-owned uploads, gallery photos, and the site cover.
Aisle Meta API
Service discovery and connectivity checks.
Aisle Parties API
Named households whose members reply together. Codes and guest sessions are managed by your application.
Aisle Payments API
Create guest checkouts and read the wedding-scoped payment ledger.
Aisle Payouts API
Connect and inspect the couple payout account.
Aisle Recommendations API
Recommendations and frequently asked questions.
Aisle Registry API
Registry items and settled contribution ledger views.
Aisle RSVP API
Read and record guest replies and event invitations.
Aisle Site API
Guest-site content and publication.
Aisle Statistics API
Canonical wedding counts and settled money totals.
Aisle Stays API
Properties, rooms, rates, payment schedules, and stay dates.
Aisle Travel API
Airports and their transport options.
Aisle Wedding API
Wedding identity and dates.
Scroll within the panel for all 18 ·
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.
aisle-wedding-create-guest-assign-room
AGENT SKILLPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
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.
Aisle Wedding 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.
Aisle API Rules
SPECTRALJSON Schema 6
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.
Event
JSON SCHEMAGuestCreate
JSON SCHEMAGuestImportRow
JSON SCHEMAGuestPatch
JSON SCHEMAGuest
JSON SCHEMAWedding
JSON SCHEMASecurity 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.
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 Aisle — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Commercial 4
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/aisle-wedding · machine-readable index on apis.io
This is an independent, third-party profile of Aisle, 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.