Lootex · Authentication Profile

Lootex Authentication

Authentication

Authentication profile assembled from Lootex's open-source core and Forge developer documentation. Two distinct surfaces existed: the marketplace backend used Web3 wallet signature authentication issuing JWTs, while the Forge minting/developer API used per-application API keys issued after registration.

Lootex declares 3 security scheme(s) across its OpenAPI definitions.

CompanyNFTMarketplaceWeb3BlockchainDigital AssetsMinting

Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

Wallet signature (SIWE-style) web3-signature

JWT bearer http

scheme: bearer · in: header ()

Forge API key apiKey

· in: header ()

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://github.com/lootex-io/lootex-core
name: Lootex Authentication
description: >-
  Authentication profile assembled from Lootex's open-source core and Forge
  developer documentation. Two distinct surfaces existed: the marketplace
  backend used Web3 wallet signature authentication issuing JWTs, while the
  Forge minting/developer API used per-application API keys issued after
  registration.
schemes:
- type: web3-signature
  name: Wallet signature (SIWE-style)
  description: >-
    Users authenticate by signing a challenge with their Web3 wallet; the
    backend verifies the signature and issues a JWT for subsequent requests.
  in: null
  source: https://github.com/lootex-io/lootex-core
- type: http
  scheme: bearer
  bearer_format: JWT
  name: JWT bearer
  description: >-
    Session JWT returned after wallet authentication, presented as a Bearer
    token on marketplace API calls.
  in: header
  location: Authorization
  source: https://github.com/lootex-io/lootex-core
- type: apiKey
  name: Forge API key
  description: >-
    The Forge developer/minting API required each client to register their
    application and request an API key. The Forge developer portal
    (docs.forge.lootex.dev) is no longer resolving.
  in: header
  location: null
  source: https://github.com/Howard86/lootex-api
notes: >-
  No OpenAPI/Swagger definition is published, so securitySchemes could not be
  derived from a spec. This profile is grounded in the public repositories and
  developer documentation only.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
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 security artifact

curl "https://apis.io/api/v1/security/lootex-authentication"

All security posture

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

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.