Lithium Finance

Lithium Finance is a decentralized asset-pricing protocol that combines machine learning with collective intelligence to value illiquid assets, with an initial focus on NFTs. Quantitative models analyze historical trading data to produce a base valuation and to flag cases where machine learning struggles — such as rare NFTs with little trading history — and the protocol then incentivizes a community of Price Experts to submit pricing estimates through on-chain Pricing Quests. Two ecosystem roles drive the network: Price Seekers (data consumers such as projects, lenders, issuers and analysts) fund prize pools to post asset-pricing enquiries, and Price Experts (brokers, traders and market participants) answer them for bounties. The economy runs on the LITH token plus non-transferable Reputation Points, and the protocol is governed by the Lithium DAO via Snapshot. The public surface is a set of Solidity Enquiry Pool, Reputation and LITH token contracts rather than a hosted web API.

Lithium Finance is profiled on the APIs.io network. Tagged areas include Company, Crypto, DeFi, Oracles, and NFT.

Lithium Finance’s developer surface includes documentation, getting-started guide, support, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub

17.0/100 emerging ▬ flat Agent 0/100 human only open core · MIT Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

0 APIs

Company Crypto DeFi Oracles NFTAsset ValuationSmart Contracts Machine-Learning DAO Blockchain

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 17.0/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 4.8 / 20

Access Clarity 4.2 / 20

Operational Transparency 1.7 / 13

Contract Governance 0.5 / 12

Discoverability 5.7 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

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.

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 github.com/api-evangelist/lith: open an issue to ask a question, or submit a pull request to add artifacts. 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.

Lith Domain Security

TLSv1.3

SECURITY

Lith Vulnerability Disclosure

Hackerone

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

SourceCode

SourceCode

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

IssueTracker

IssueTracker

Support

Support

Community

Community

Commercial 3

Pricing, plans, and the legal terms of use

License

License

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Twitter

Twitter

Other 2

Properties that don't map to a standard resource type

Telegram

Governance

Governance

Source (apis.yml)

aid: lith
name: Lithium Finance
description: 'Lithium Finance is a decentralized asset-pricing protocol that combines machine learning with collective intelligence
  to value illiquid assets, with an initial focus on NFTs. Quantitative models analyze historical trading data to produce
  a base valuation and to flag cases where machine learning struggles — such as rare NFTs with little trading history — and
  the protocol then incentivizes a community of Price Experts to submit pricing estimates through on-chain Pricing Quests.
  Two ecosystem roles drive the network: Price Seekers (data consumers such as projects, lenders, issuers and analysts) fund
  prize pools to post asset-pricing enquiries, and Price Experts (brokers, traders and market participants) answer them for
  bounties. The economy runs on the LITH token plus non-transferable Reputation Points, and the protocol is governed by the
  Lithium DAO via Snapshot. The public surface is a set of Solidity Enquiry Pool, Reputation and LITH token contracts rather
  than a hosted web API.'
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://lith.finance/static/images/lithium-finance-socials-banner.png
url: https://raw.githubusercontent.com/api-evangelist/lith/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- pantera-capital
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Crypto
- DeFi
- Oracles
- NFT
- Asset Valuation
- Smart Contracts
- Machine-Learning
- DAO
- Blockchain
tags_raw:
- Company
- Crypto
- DeFi
- Oracles
- NFT
- Asset Valuation
- Smart Contracts
- Machine Learning
- DAO
- Blockchain
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: IssueTracker
  url: https://github.com/Lithium-Finance/lithium-smart-contracts/issues
- type: License
  name: MIT
  url: https://github.com/Lithium-Finance/lithium-smart-contracts/blob/main/LICENSE
- type: Website
  url: https://lith.finance/
- type: Documentation
  url: https://lith.finance/docs-sub/index
- type: GettingStarted
  url: https://lith.finance/docs-sub/overview/how-it-works
- type: GitHubOrganization
  url: https://github.com/Lithium-Finance
- type: SourceCode
  url: https://github.com/Lithium-Finance/lithium-smart-contracts
- type: Support
  url: https://discord.gg/lithiumfinanceofficial
- type: Community
  url: https://lith.finance/forum-sub/index
- type: Twitter
  url: https://twitter.com/lithiumfinance
- type: Telegram
  url: https://t.me/lithiumfinanceofficial
- type: Governance
  url: https://snapshot.org/#/lithfinance.eth
- type: TermsOfService
  url: https://lith-finance.notion.site/Lithium-Finance-Terms-of-Service-c77aa2f729f74045b7871c4326c63e68
- type: PrivacyPolicy
  url: https://lith-finance.notion.site/Lithium-Finance-Privacy-Policy-57cc4ab92c4c4eca83fc794c3f66e491
- type: Security
  url: https://lith.finance/docs-sub/guides/bug-bounty
- type: VulnerabilityDisclosure
  url: security/lith-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/lith-domain-security.yml
- type: WellKnown
  url: well-known/lith-well-known.yml
- type: Conformance
  url: conformance/lith-conformance.yml
- type: Lifecycle
  url: lifecycle/lith-lifecycle.yml
- type: Packages
  url: packages/lith-packages.yml
- type: LLMsTxt
  url: llms/lith-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/lith"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/lith/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.