Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lens Protocol

Lens Protocol is an onchain social graph and a developer platform for building social applications where users own their profile, content, and relationships. Originally launched on Polygon PoS, Lens has since evolved into Lens Chain — an L2 zkEVM rollup purpose-built for social — with the Lens v3 contracts redesigned around primitives like Accounts, Apps, Feeds, Groups, Graphs, and Actions. Developers integrate Lens through the Lens API (a GraphQL gateway over the indexed chain state), the Lens TypeScript SDK and React SDK, the underlying smart contracts, and an authentication layer that issues short-lived auth tokens after a SIWE-style signature. Lens powers social clients (Hey, Orb, Tape, Buttrfly), creator tools, and composable mini-apps that share the same onchain social graph.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Lens Protocol the way a machine reads it — 11 machine-readable artifacts across 6 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 — Lens Protocol scores 22.7/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 22.7/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 3.5 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 3.4 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 7/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Lens Protocol

Each block below is one kind of artifact we hold for Lens Protocol. 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 6

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.

Lens API (GraphQL)

The Lens API is a hosted GraphQL endpoint that indexes the Lens Chain contracts and exposes queries and mutations for accounts, posts (publications), feeds, follows, groups, app...

Lens TypeScript SDK

The Lens SDK is the official TypeScript client for the Lens API. It wraps GraphQL operations behind typed functions, handles auth token lifecycle, encodes content metadata (Lens...

Lens React SDK

The Lens React SDK provides React hooks (useAccount, usePosts, useFollow, useLogin, etc.) layered on top of the Lens client SDK, so frontend developers can wire Lens primitives ...

Lens Protocol Smart Contracts

The Lens v3 smart contracts implement the onchain social graph on Lens Chain. Core primitives include Accounts (user identity owned by a wallet), Apps (namespaces that publish c...

Lens Authentication

Lens authentication uses a sign-in-with-Ethereum style challenge: a client requests a signing message from the Lens API, the user signs it with their wallet, and the API returns...

Lens Storage & Metadata

Lens content (post body, media, profile metadata) is stored as JSON following the Lens Metadata Standards and pinned to decentralized storage (IPFS, Arweave, or Lens-hosted stor...

GraphQL 1

Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.

GraphQL schemas published by this provider.

Lens Protocol GraphQL API

The Lens API is a hosted GraphQL endpoint that indexes the Lens

GRAPHQL

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 six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Lens Protocol Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Security Posture 1

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.

Lens Protocol Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Every other property we hold for Lens Protocol — 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.

Documentation 1

Reference material describing how the API behaves

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 3

The organization behind the API

Other 3

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/lens-protocol · machine-readable index on apis.io