Userlens

Userlens is an AI-native customer success platform for B2B SaaS that deploys LLM-powered agents to monitor every customer account, predict churn from actual product usage, and surface expansion opportunities. It ingests product analytics, CRM data, and business context for AI health scores, account-level analytics, and proactive alerts, and exposes a Write-Code-authenticated Events API (identify, group, track, and batched SDK event forwarding) plus JavaScript SDKs for instrumentation. Founded in 2025 (Y Combinator Spring 2026 batch), based in San Francisco and Helsinki.

Userlens publishes 1 API contract indexed on the APIs.io network: Events API. Tagged areas include Company, Customer Success, Product Analytics, AI Agents, and Churn Prediction.

The Userlens catalog on APIs.io includes 1 Spectral governance ruleset.

Userlens’ developer surface includes engineering blog, documentation, API reference, getting-started guide, pricing, authentication, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

37.8/100 thin ▬ flat Agent 21/100 agent aware Front door AI 3/6 light Heartbeat 90/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 MCP Servers 2 Agent Skills

Company Customer Success Product Analytics AI Agents Churn Prediction Event Tracking B2B SaaS Account Intelligence

Kin Score

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

Composite quality — 37.8/100 · thin

Contract Quality 2.8 / 19

Developer Ergonomics 7.8 / 15

Access Clarity 7.9 / 15

Operational Transparency 0.5 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 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 5 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/userlens/"><img src="https://apis.io/badge/userlens/card.svg" alt="Userlens 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):

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)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 14.8 — up to +21.3 composite points
Operational Transparency scores 5.3 — up to +12.3 composite points
Developer Ergonomics scores 51.8 — up to +9.6 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/userlens/apis.yml: open an issue on github.com/api-evangelist/userlens 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 →

Standards implemented 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Userlens Events API

User identification, company grouping, and event ingestion

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Userlens Events API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Userlens MCP Server

Remote MCP server over HTTP; 4 tools listed. A candidate, not confirmed as published by the provider.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Instrument a user lifecycle in Userlens

AGENT SKILL

Forward Userlens SDK events through a backend proxy

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Userlens API Rules

51 rules · 49 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Userlens Events Overlay

4 actions · update · userlens-events-openapi.yml

DERIVED

Security Posture 2

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

Userlens Authentication

http · 1 scheme

SECURITY

Userlens Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

WellKnown

MCPServer

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Compliance

Compliance

Authentication

Authentication

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: userlens
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  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/userlens.png
name: Userlens
description: Userlens is an AI-native customer success platform for B2B SaaS that deploys LLM-powered agents to monitor every
  customer account, predict churn from actual product usage, and surface expansion opportunities. It ingests product analytics,
  CRM data, and business context for AI health scores, account-level analytics, and proactive alerts, and exposes a Write-Code-authenticated
  Events API (identify, group, track, and batched SDK event forwarding) plus JavaScript SDKs for instrumentation. Founded
  in 2025 (Y Combinator Spring 2026 batch), based in San Francisco and Helsinki.
url: https://raw.githubusercontent.com/api-evangelist/userlens/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- y-combinator
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: gitbook
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Customer Success
- Product Analytics
- AI Agents
- Churn Prediction
- Event Tracking
- B2B SaaS
- Account Intelligence
apis:
- aid: userlens:userlens-events-api
  name: Userlens Events API
  description: User identification, company grouping, and event ingestion
  humanURL: https://userlens.gitbook.io/userlens-analytics
  baseURL: https://events.userlens.io
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/userlens-events-api-openapi.yml
  - type: Documentation
    url: https://userlens.gitbook.io/userlens-analytics
  - type: APIReference
    url: https://userlens.gitbook.io/userlens-analytics/guides/api-reference
common:
- url: https://userlens.io/news
  type: Blog
- url: https://userlens.io/news/rss.xml
  type: BlogRSS
- type: Overlay
  url: overlays/userlens-events-overlay.yaml
- type: DomainSecurity
  url: security/userlens-domain-security.yml
- url: https://userlens.io
  type: Website
- url: https://userlens.gitbook.io/userlens-analytics
  type: Documentation
- url: https://userlens.gitbook.io/userlens-analytics/guides/api-reference
  type: APIReference
- url: https://userlens.gitbook.io/userlens-analytics/getting-started/http-api
  type: GettingStarted
- url: https://userlens.io/pricing
  type: Pricing
- url: https://userlens.io/blog
  type: Blog
- url: https://app.userlens.io/
  type: Login
- url: https://userlens.io/terms-of-service
  type: TermsOfService
- url: https://userlens.io/privacy-policy
  type: PrivacyPolicy
- url: https://github.com/wudpecker
  type: GitHubOrganization
- url: llms/userlens-llms.txt
  type: LLMsTxt
- url: packages/userlens-packages.yml
  type: Packages
- url: packages/userlens-packages.yml
  type: SDKs
- url: well-known/userlens-well-known.yml
  type: WellKnown
- url: mcp/userlens-mcp.yml
  type: MCPServer
- url: conformance/userlens-conformance.yml
  type: Conformance
- url: https://userlens.io/llms.txt
  type: Compliance
- url: errors/userlens-problem-types.yml
  type: ErrorCatalog
- url: lifecycle/userlens-lifecycle.yml
  type: Lifecycle
- url: authentication/userlens-authentication.yml
  type: Authentication
- url: conventions/userlens-conventions.yml
  type: Conventions
- url: data-model/userlens-data-model.yml
  type: DataModel
- url: skills/_index.yml
  type: AgentSkill
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 16
  pass: local-v1

Userlens API — frequently asked questions

Does Userlens have an API?

Yes. APIs.io lists 1 API from Userlens, including Userlens Events API.

Is there an OpenAPI specification for the Userlens API?

Yes. APIs.io indexes 1 OpenAPI specification for Userlens, each linked for download from this page.

How do I authenticate with the Userlens API?

Userlens uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Userlens Authentication.

Does Userlens have an MCP server?

Yes. APIs.io lists 1 MCP server for Userlens: Remote MCP server over HTTP; 4 tools listed. A candidate, not confirmed as published by the provider.

Is the Userlens API ready for AI agents?

Userlens has a Kin Score of 37.8 out of 100 (thin) and an Agent Readiness score of 21.0 (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/userlens"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/userlens/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.