Mosey
Mosey is a business compliance platform that helps multi-state companies open and manage state and local tax, HR, payroll, insurance, and registration accounts. The Mosey API is a composable set of OpenAPI 3.1 endpoints that let software platforms embed state compliance into their own products: sign up or authenticate a legal entity, register the states it operates in, generate and resolve compliance tasks, receive physical mail, and securely manage state-agency logins via short-lived hosted sessions. Authentication is OAuth2 (password grant). Mosey partnered with Gusto, Stripe, and Sequoia Consulting Group and was subsequently acquired by Gusto. This profile was surfaced as a Canaan Partners portfolio company and enriched by the API Evangelist pipeline from Mosey's public OpenAPI and developer documentation.
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 Mosey the way a machine reads it — 28 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 — Mosey scores 36.1/100 (thin), with a separate agent-readiness read of 26/100 (agent aware). 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 Mosey'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/mosey/"
title="Mosey on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mosey.svg"
alt="Mosey Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/mosey/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mosey/"
title="Mosey on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mosey/card.svg"
alt="Mosey 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 Mosey
Each block below is one kind of artifact we hold for Mosey. 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 12
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.
Mosey Accounts API
The Accounts API from Mosey — 7 operation(s) for accounts.
Mosey Agency Accounts API
The Agency Accounts API from Mosey — 2 operation(s) for agency accounts.
Mosey Auth API
The Auth API from Mosey — 2 operation(s) for auth.
Mosey Documents API
The Documents API from Mosey — 1 operation(s) for documents.
Mosey Handbook API
The Handbook API from Mosey — 3 operation(s) for handbook.
Mosey Legal Entity API
The Legal Entity API from Mosey — 2 operation(s) for legal entity.
Mosey Locations API
The Locations API from Mosey — 7 operation(s) for locations.
Mosey Logins API
The Logins API from Mosey — 4 operation(s) for logins.
Mosey Mail API
The Mail API from Mosey — 2 operation(s) for mail.
Mosey Regions API
The Regions API from Mosey — 2 operation(s) for regions.
Mosey Signup API
The Signup API from Mosey — 3 operation(s) for signup.
Mosey Tasks API
The Tasks API from Mosey — 9 operation(s) for tasks.
Scroll within the panel for all 12 ·
Open Collections 13
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).
API Collection
OPEN COLLECTIONMosey Accounts API
OPEN COLLECTIONMosey Accounts Agency Accounts API
OPEN COLLECTIONMosey Accounts Auth API
OPEN COLLECTIONMosey Accounts Documents API
OPEN COLLECTIONMosey Accounts Handbook API
OPEN COLLECTIONMosey Accounts Legal Entity API
OPEN COLLECTIONMosey Accounts Locations API
OPEN COLLECTIONMosey Accounts Logins API
OPEN COLLECTIONMosey Accounts Mail API
OPEN COLLECTIONMosey Accounts Regions API
OPEN COLLECTIONMosey Accounts Signup API
OPEN COLLECTIONMosey Accounts Tasks API
OPEN COLLECTIONScroll within the panel for all 13 ·
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.
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 Mosey — 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 3
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 3
Pricing, plans, and the legal terms of use
Company 2
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/mosey · machine-readable index on apis.io
This is an independent, third-party profile of Mosey, 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.