Lootex
Lootex is a Web3 infrastructure and AI application development company with eight years in the blockchain space, backed by 500 Global. It built a multi-chain NFT marketplace (Seaport protocol with aggregator support), the Lootex Studio minting tool, the Biru social platform, and Lootex Plus (an API and SDK offering to mint, trade, and integrate NFTs into apps and games). Its core marketplace infrastructure — a NestJS backend and Next.js frontend with blockchain event indexing and Web3 wallet authentication — is published as open source under Apache-2.0. Lootex is now sunsetting its consumer products (marketplace, Studio, and Biru wind down on 2026-04-04; assets stay in users' own non-custodial wallets) and pivoting to full-stack AI/Web3 development partnerships and open-source contributions.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Lootex 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 — Lootex scores 14.5/100 (minimal), with a separate agent-readiness read of 10/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Lootex
Each block below is one kind of artifact we hold for Lootex. 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.
Resources
Every other property we hold for Lootex — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lootex · machine-readable index on apis.io