LeapYear Technologies

LeapYear Technologies built an enterprise platform for differentially private analytics and machine learning, letting organizations compute over highly sensitive data and share it across internal silos and external partners with mathematically proven privacy guarantees. LeapYear Core was licensed, self-hosted software rather than a public multi-tenant API: customers ran their own server and reached it through a first-party Python client, with every computation drawing down a quantified privacy exposure budget enforced by the server. Snowflake announced its intent to acquire LeapYear on 2023-02-07 and closed on 2023-02-10 for USD 62.0 million in cash, primarily for talent and developed technology, folding the differential privacy capability into its Global Data Clean Room offering. The company no longer operates independently, leapyear.io is now a Snowflake-controlled redirect, and the only surviving first-party documentation is the Python client API reference on its readthedocs host.

LeapYear Technologies is profiled on the APIs.io network. Tagged areas include Company, AI Infrastructure, Differential Privacy, Privacy, and Machine Learning.

LeapYear Technologies’ developer surface includes documentation, API reference, getting-started guide, authentication, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

14.4/100 emerging ▬ flat Agent 5/100 agent aware library Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company AI Infrastructure Differential Privacy Privacy Machine LearningData Clean RoomsPrivacy Enhancing Technologies Acquired

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 14.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 8.1 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 4.7 / 9

Regulatory Posture 1.6 / 15

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/leapyear-technologies/"><img src="https://apis.io/badge/leapyear-technologies/card.svg" alt="LeapYear Technologies 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/leapyear-technologies/apis.yml: open an issue on github.com/api-evangelist/leapyear-technologies to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Leapyear Technologies Authentication

2 schemes

SECURITY

Leapyear Technologies Domain Security

no transport/DNS hardening detected

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

ErrorCatalog

Conventions

Conventions

Lifecycle

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Acquisition

Acquisition

Source (apis.yml)

aid: leapyear-technologies
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/leapyear-technologies.png
name: LeapYear Technologies
description: 'LeapYear Technologies built an enterprise platform for differentially private analytics and machine learning,
  letting organizations compute over highly sensitive data and share it across internal silos and external partners with mathematically
  proven privacy guarantees. LeapYear Core was licensed, self-hosted software rather than a public multi-tenant API: customers
  ran their own server and reached it through a first-party Python client, with every computation drawing down a quantified
  privacy exposure budget enforced by the server. Snowflake announced its intent to acquire LeapYear on 2023-02-07 and closed
  on 2023-02-10 for USD 62.0 million in cash, primarily for talent and developed technology, folding the differential privacy
  capability into its Global Data Clean Room offering. The company no longer operates independently, leapyear.io is now a
  Snowflake-controlled redirect, and the only surviving first-party documentation is the Python client API reference on its
  readthedocs host.'
url: https://raw.githubusercontent.com/api-evangelist/leapyear-technologies/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bain-capital-ventures
x-tier: stub
x-tier-reason: portfolio-lead
x-status: acquired
x-acquired-by: snowflake
x-acquired-date: '2023-02-10'
x-operating: false
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- AI Infrastructure
- Differential Privacy
- Privacy
- Machine Learning
- Data Clean Rooms
- Privacy Enhancing Technologies
- Acquired
tags_raw:
- Company
- Ai Infrastructure
- Differential Privacy
- Data Privacy
- Machine Learning
- Data Clean Rooms
- Privacy Enhancing Technologies
- Acquired
- Machine-Learning
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://leapyear.io/
- type: Documentation
  url: https://leapyear-python-docs.readthedocs-hosted.com/en/4.1.1/
- type: APIReference
  url: https://leapyear-python-docs.readthedocs-hosted.com/en/4.1.1/api.html
- type: GettingStarted
  url: https://leapyear-python-docs.readthedocs-hosted.com/en/4.1.1/tutorial.html
- type: Packages
  url: packages/leapyear-technologies-packages.yml
- type: SDKs
  url: packages/leapyear-technologies-packages.yml
- type: Authentication
  url: authentication/leapyear-technologies-authentication.yml
- type: ErrorCatalog
  url: errors/leapyear-technologies-error-codes.yml
- type: Conventions
  url: conventions/leapyear-technologies-conventions.yml
- type: Lifecycle
  url: lifecycle/leapyear-technologies-lifecycle.yml
- type: DomainSecurity
  url: security/leapyear-technologies-domain-security.yml
- type: LLMsTxt
  url: llms/leapyear-technologies-llms.txt
- type: Acquisition
  url: https://www.snowflake.com/en/blog/snowflake-to-acquire-leapyear/
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LeapYear Technologies API — frequently asked questions

How do I authenticate with the LeapYear Technologies API?

LeapYear Technologies uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Leapyear Technologies Authentication.

Is the LeapYear Technologies API ready for AI agents?

LeapYear Technologies has a Kin Score of 14.4 out of 100 (emerging) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/leapyear-technologies"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/leapyear-technologies/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/leapyear-technologies/evidence"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.