Shakepay
Shakepay (Shake Labs Inc.) is a regulated Canadian cryptocurrency platform headquartered in Montreal, Quebec, serving 1,500,000+ Canadians with commission-free buying, selling, and on-chain movement of Bitcoin, Ethereum, and USDC via Interac e-Transfer. Beyond trading it offers a Visa prepaid card that earns up to 1.5% back in bitcoin (#shakepaid), recurring dollar-cost- averaging buys, interest paid weekly in bitcoin on CAD/USD balances, peer-to- peer transfers, bill pay, and the daily ShakingSats reward. Shakepay is a CIRO member, a registered Investment Dealer with the AMF, registered with securities regulators across all Canadian provinces/territories, and a FINTRAC money-services business. It does not currently publish a public developer API; it runs an experimental agent-access MCP surface (mcp.shakepay.com) alongside a public status page, security.txt bug-bounty program, and llms.txt reference.
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 Shakepay the way a machine reads it — 3 machine-readable artifacts, 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 — Shakepay scores 30.5/100 (thin), with a separate agent-readiness read of 18/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.
How we profile Shakepay
Each block below is one kind of artifact we hold for Shakepay. 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.
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.
shakepay-mcp.yml
MCP SERVERSecurity 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.
Resources
Every other property we hold for Shakepay — 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
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/shakepay · machine-readable index on apis.io