Akia (The Akia Syndicate) is a San Francisco based hospitality technology company whose AI agent platform automates the guest lifecycle for hotels and vacation rentals — guest messaging over SMS/WhatsApp/web chat, an AI voice agent, digital check-in and pre-registration through Mini Apps, guidebooks, upsells, tipping, tasks, team chat, keyless entry, surveys, reputation management and marketing campaigns. Akia synchronizes with more than fifty property management, smart-lock, payment and operations systems (Opera, Mews, Cloudbeds, Apaleo, StayNTouch, Track, Guesty, RemoteLock, Brivo, Salto KS, Veriff, Stripe) and exposes a partner-gated REST API at api.akia.com/v3 with OAuth 2.0 authorization, a published scope catalog, outbound webhook subscriptions, an embeddable web chat and partner embed SDK, and a remote MCP server at sys.akia.ai/mcp for agent access.
Akia is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Hospitality, Hotels, Vacation Rentals, and Guest Experience.
The Akia catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Akia’s developer surface includes documentation, API reference, getting-started guide, engineering blog, pricing, signup flow, support, and 23 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/akia/"><img src="https://apis.io/badge/akia/card.svg" alt="Akia on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Akia's REST API (version 3, with version 4 resources for mini apps and reservations) for creating and searching customers and reservations, sending guest messages, reading prope...
Akia's remote Model Context Protocol server, advertised through RFC 9728 OAuth protected-resource metadata at api.akia.com and sys.akia.com. The endpoint requires a Bearer token...
aid: akia
name: Akia
description: Akia (The Akia Syndicate) is a San Francisco based hospitality technology company whose AI agent platform automates
the guest lifecycle for hotels and vacation rentals — guest messaging over SMS/WhatsApp/web chat, an AI voice agent, digital
check-in and pre-registration through Mini Apps, guidebooks, upsells, tipping, tasks, team chat, keyless entry, surveys,
reputation management and marketing campaigns. Akia synchronizes with more than fifty property management, smart-lock, payment
and operations systems (Opera, Mews, Cloudbeds, Apaleo, StayNTouch, Track, Guesty, RemoteLock, Brivo, Salto KS, Veriff,
Stripe) and exposes a partner-gated REST API at api.akia.com/v3 with OAuth 2.0 authorization, a published scope catalog,
outbound webhook subscriptions, an embeddable web chat and partner embed SDK, and a remote MCP server at sys.akia.ai/mcp
for agent access.
url: https://raw.githubusercontent.com/api-evangelist/akia/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
probe_state: covered
source:
- plans
- authentication
- scopes
- security
generated: '2026-11-06'
method: derived
image: https://www.akia.com/icon.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
x-enrichment:
date: '2026-08-06'
status: enriched
artifacts_added: 16
pass: local-v1
x-coverage:
state: covered
reason: covered
detail: Akia's developer reference at api.akia.com/docs is fully server-rendered and readable, and the OAuth, security.txt,
llms.txt and MCP surfaces were all harvested verbatim; the one real gap is that no OpenAPI is published anywhere on the
API host, so no spec has been authored on Akia's behalf.
evidence:
- url: https://api.akia.com/docs
status: 200
- url: https://api.akia.com/openapi.json
status: 200
- url: https://sys.akia.ai/mcp
status: 401
checked: '2026-08-06'
created: '2026-08-06'
modified: '2026-08-06'
tags:
- Company
- Hospitality
- Hotels
- Vacation Rentals
- Guest Experience
- Messaging
- Artificial Intelligence
- Agents
- Property Management
- Check-in
tags_raw:
- Company
- Hospitality
- Hotels
- Vacation Rentals
- Guest Experience
- Messaging
- Artificial Intelligence
- Agents
- Property Management
- Check-In
apis:
- aid: akia:akia-api
name: Akia API
description: Akia's REST API (version 3, with version 4 resources for mini apps and reservations) for creating and searching
customers and reservations, sending guest messages, reading properties, generating and reading mini-app and agreement
sessions, posting team-chat messages, building audiences and running reports. Authorization is OAuth 2.0 (RFC 6749) authorization-code
with refresh tokens and a published scope catalog. Access is granted to select partners on request via partnerships@akia.com.
humanURL: https://api.akia.com/docs
baseURL: https://api.akia.com/v3/
tags:
- Guest Messaging
- Reservations
- Customers
- Hospitality
x-evidence:
verified: '2026-08-06'
method: fetched-docs
docs_url: https://api.akia.com/docs
docs_http_status: 200
documents: Server-rendered developer reference listing 30 operations across Audience, Context, Customer, Mini Apps, Properties,
Report, Reservations and Team Chat, each with method, path, required scope, request and response parameter tables and
a JSON example.
base_url_source: 'Documented on https://api.akia.com/docs — "All calls in this documentation expect either GET or POST
requests made against the following base URL: https://api.akia.com/v3/"'
access: Partner-gated — "Access to Akia's API is currently available to select partners. Please reach out to partnerships@akia.com
if you have a request."
machine_readable_spec: none published — /openapi.json, /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs, /redoc
on api.akia.com all return the SPA login shell (HTTP 200, text/html)
properties:
- type: Documentation
url: https://api.akia.com/docs
- type: APIReference
url: https://api.akia.com/docs
- type: GettingStarted
url: https://api.akia.com/docs/introduction
- type: Authentication
url: https://api.akia.com/docs/authentication
- type: OAuthScopes
url: https://api.akia.com/docs/scopes
- type: RateLimits
url: https://api.akia.com/docs/rate_limits
- type: Webhooks
url: https://api.akia.com/docs/webhooks
- aid: akia:akia-mcp
name: Akia MCP Server
description: Akia's remote Model Context Protocol server, advertised through RFC 9728 OAuth protected-resource metadata
at api.akia.com and sys.akia.com. The endpoint requires a Bearer token issued by the Akia authorization server at sys.akia.ai,
which supports dynamic client registration (RFC 7591) and PKCE S256. The advertised resource scopes are customers:read
and messages:read.
humanURL: https://api.akia.com/docs
baseURL: https://sys.akia.ai/mcp
tags:
- MCP
- Agents
x-evidence:
verified: '2026-08-06'
method: probed
url: https://sys.akia.ai/mcp
http_status: 401
www_authenticate: Bearer resource_metadata="https://sys.akia.ai/.well-known/oauth-protected-resource"
note: tools/list and initialize both return 401 with an RFC 9728 challenge — the server is genuinely published but the
tool schemas require an authenticated introspection.
properties:
- type: MCPServer
url: mcp/akia-mcp.yml
- type: Authentication
url: authentication/akia-authentication.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Plans
url: plans/akia-plans-pricing.yml
- type: TrustCenter
url: security/akia-trust-center.yml
- type: VulnerabilityDisclosure
url: security/akia-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/akia-domain-security.yml
- type: Website
url: https://www.akia.com/
- type: DeveloperPortal
url: https://api.akia.com/docs
- type: Documentation
url: https://api.akia.com/docs
- type: APIReference
url: https://api.akia.com/docs
- type: GettingStarted
url: https://api.akia.com/docs/introduction
- type: Blog
url: https://www.akia.com/blog
- type: Pricing
url: https://www.akia.com/pricing
- type: SignUp
url: https://www.akia.com/demo
- type: Login
url: https://sys.akia.ai
- type: Support
url: https://www.akia.com/contact
- type: TermsOfService
url: https://www.akia.com/msa
- type: PrivacyPolicy
url: https://www.akia.com/privacy
- type: Security
url: https://www.akia.com/security
- type: Compliance
url: https://www.akia.com/security
- type: Integrations
url: https://www.akia.com/marketplace
- type: WellKnown
url: well-known/akia-well-known.yml
- type: SecurityTxt
url: well-known/akia-security.txt
- type: LLMsTxt
url: llms/akia-llms.txt
- type: MCPServer
url: mcp/akia-mcp.yml
- type: Authentication
url: authentication/akia-authentication.yml
- type: OAuthScopes
url: scopes/akia-scopes.yml
- type: Conformance
url: conformance/akia-conformance.yml
- type: Lifecycle
url: lifecycle/akia-lifecycle.yml
- type: Conventions
url: conventions/akia-conventions.yml
- type: Components
url: components/akia-components.yml
- type: DataModel
url: data-model/akia-data-model.yml
- type: Webhooks
url: asyncapi/akia-webhooks.yml
Akia API — frequently asked questions
Does Akia have an API?
Yes. APIs.io lists 2 APIs from Akia, including Akia API and Akia MCP Server.
How do I authenticate with the Akia API?
Akia documents its authentication (oauth2 · 3 schemes). The details are profiled on APIs.io as Akia Authentication.
How much does the Akia API cost?
Akia publishes its prices; its Basic plan is Talk to Sales as of 2026-10-07. APIs.io lists 3 pricing plans for Akia, with each plan's price, limits and inclusions under Pricing on this page.
Does Akia have an MCP server?
Yes. APIs.io lists 1 MCP server for Akia: Remote MCP server at sys.akia.ai over HTTP.
Is the Akia API ready for AI agents?
Akia has a Kin Score of 55.7 out of 100 (strong) and an Agent Readiness score of 47.1 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: