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
Level website screenshot

Level

Level is a stablecoin protocol that issued lvlUSD, a stablecoin fully backed by USDC and USDT which were deployed into blue-chip lending protocols (Aave and the Morpho Steakhouse USDC vault) to generate yield. Lending yield was passed back to holders through an ERC-4626 staking mechanism: lvlUSD could be staked for slvlUSD, a yield-accruing token that appreciates as the protocol distributes yield into the staking contract. Both tokens were transferable and integrated across DeFi venues including Morpho, Pendle, Spectra and Curve, with LayerZero OFT adapters bridging them to Base. Level exposes no public HTTP API — its programmable surface is a set of audited Ethereum mainnet smart contracts (lvlUSD, slvlUSD, LevelMinting, LevelStakingPool, LevelUsdPointsFarm, LevelReserveLens) documented in GitBook and published on GitHub. In September 2025 the team announced it was joining the Sky (fka MakerDAO) ecosystem as part of Grove and that the Level protocol is being sunset: mints paused, redemptions made public and fixed 1:1, cooldowns cut to two seconds, final yield distribution on 2025-10-02, and the front end retired on 2025-12-15 with contract-level redemption remaining available indefinitely.

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 Level the way a machine reads it — 2 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 — Level scores 18.8/100 (emerging), with a separate agent-readiness read of 4/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 — 18.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 3.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 4/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 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Level

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

Security 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.

Level Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Level Vulnerability Disclosure

disclosure policy published

SECURITY

Resources

Every other property we hold for Level — 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

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

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