wakato-io
Wakato provides an all‑in‑one AI‑driven business platform that consolidates website, shop, inbox, phone, ads, social media, email, calendar and bookkeeping into a single account. Users can launch AI‑built websites, apps, and commerce solutions on their own domain, with automated marketing, customer support, and financial management, all managed through intuitive AI agents.
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 wakato-io the way a machine reads it — 33 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 — wakato-io scores 47.5/100 (developing), with a separate agent-readiness read of 35/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.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from wakato-io'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/wakato-io/"
title="wakato-io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wakato-io.svg"
alt="wakato-io Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/wakato-io/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wakato-io/"
title="wakato-io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wakato-io/card.svg"
alt="wakato-io 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 wakato-io
Each block below is one kind of artifact we hold for wakato-io. 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 27
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.
wakato-io Ads API
The Ads API from wakato-io — 3 operation(s) for ads.
wakato-io Agent Mail API
The Agent Mail API from wakato-io — 7 operation(s) for agent mail.
wakato-io Agents with a Reach API
The Agents with a Reach API from wakato-io — 2 operation(s) for agents with a reach.
wakato-io Apps API
The Apps API from wakato-io — 7 operation(s) for apps.
wakato-io Assets API
The Assets API from wakato-io — 4 operation(s) for assets.
wakato-io Audiences API
Saved segments (lists) of your **Contacts**, used to target campaigns and messages across any channel. Audiences are part of Contacts (managed at `/spaces/:spaceId/contacts/audi...
wakato-io Automations API
The Automations API from wakato-io — 2 operation(s) for automations.
wakato-io Blog API
The Blog API from wakato-io — 5 operation(s) for blog.
wakato-io Booking Pages API
The Booking Pages API from wakato-io — 3 operation(s) for booking pages.
wakato-io Bookings API
The Bookings API from wakato-io — 3 operation(s) for bookings.
wakato-io Calendar API
The Calendar API from wakato-io — 2 operation(s) for calendar.
wakato-io Contacts API
People and companies in your space — the foundation everything else attaches to. Segment and target your contacts with **Audiences** and **Tags**, both managed under Contacts.
wakato-io Decks API
Presentation decks: slides of HTML and CSS in a 1280×720 frame, pictures and video from the space's Assets, speaker notes, a link per person and who watched it how far. Uses the...
wakato-io Documents API
The Documents API from wakato-io — 2 operation(s) for documents.
wakato-io Events API
What happens in your space (a new order, a booking, a form reply…) sent to your system as signed webhooks, or kept as a feed you pull. Uses the automations scope.
wakato-io Finance API
The Finance API from wakato-io — 2 operation(s) for finance.
wakato-io Forms API
The Forms API from wakato-io — 4 operation(s) for forms.
wakato-io Integrations API
The Integrations API from wakato-io — 1 operation(s) for integrations.
wakato-io Meet API
The Meet API from wakato-io — 1 operation(s) for meet.
wakato-io Messaging API
The Messaging API from wakato-io — 4 operation(s) for messaging.
wakato-io Pages API
The Pages API from wakato-io — 4 operation(s) for pages.
wakato-io Phone API
The Phone API from wakato-io — 8 operation(s) for phone.
wakato-io Secrets API
The Secrets API from wakato-io — 1 operation(s) for secrets.
wakato-io Social API
The Social API from wakato-io — 5 operation(s) for social.
wakato-io Tables API
The Tables API from wakato-io — 15 operation(s) for tables.
wakato-io Tasks API
The Tasks API from wakato-io — 3 operation(s) for tasks.
wakato-io Wallet API
The Wallet API from wakato-io — 2 operation(s) for wallet.
Scroll within the panel for all 27 ·
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 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.
Wakato Io 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.
wakato-io API Rules
SPECTRALSecurity 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 wakato-io — 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 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
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/wakato-io · machine-readable index on apis.io
This is an independent, third-party profile of wakato-io, 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.