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.
Lens Protocol is listed with 6 APIs on the APIs.io network. Tagged areas include Lens Protocol, Onchain Social, Web3, Social Graph, and Polygon.
Lens Protocol’s developer surface includes documentation, engineering blog, and 14 more developer resources.
12.6/100emerging▬ flatAgent1/100human onlyFront door AI1/6
silent
Heartbeat16/100
dormant
self hosted · MIT
Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
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/lens-protocol/"><img src="https://apis.io/badge/lens-protocol/card.svg" alt="Lens Protocol 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 Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
12 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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.
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...
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...
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 ...
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 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 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...
The Lens API is a hosted GraphQL endpoint that indexes the Lens
GRAPHQL
Lens Protocol API pricing
Not yet checked against Lens Protocol's own pricing page. Compiled by API Evangelist on 2026-05-22; confirm before you rely on a figure. A free plan or tier is listed.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: