Demox Labs

Demox Labs is a San Francisco company building privacy infrastructure for zero-knowledge (ZK) blockchains, starting with the Aleo network. It is the maker of Leo Wallet, a privacy-focused, zero-knowledge cryptocurrency wallet that constructs transactions locally on the user's device and lets holders conceal or disclose any component of a transaction before it is verified on chain. Demox ships developer tooling for the Aleo and Polygon Miden ecosystems: the Aleo SDK and Miden SDK (WebAssembly builds), the Aleo and Miden wallet adapters (modular TypeScript adapters and React components for connecting dApps to compatible wallets), and the public Aleo RPC API, a free JSON-RPC 2.0 endpoint for reading blocks, transactions, transitions, records, programs, mappings, NFTs, and staking data from the Aleo network. Leo Wallet is transitioning to Shield, a next-generation Aleo privacy wallet built by Provable.

Demox Labs publishes 1 API on the APIs.io network. Tagged areas include Company, Blockchain, Zero Knowledge, Cryptocurrency, and Wallets.

Demox Labs’ developer surface includes documentation, getting-started guide, API reference, engineering blog, support, signup flow, authentication, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub

28.2/100 thin ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Blockchain Zero Knowledge Cryptocurrency Wallets Privacy Web3 Developer Tools SDK JSON-RPC

Kin Score

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

Composite quality — 28.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 10.1 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.5 / 10

Discoverability 6.5 / 9

Regulatory Posture 5.9 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 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

Regulatory Posture applies to this provider. Its tags matched the Payments 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/.

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/demox-labs: 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 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Aleo RPC API

Free public JSON-RPC 2.0 API for reading the Aleo zero-knowledge blockchain — latest blocks and heights, transactions and transitions, records, deployed programs, mapping values...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Demox Labs Authentication

none · 1 scheme

SECURITY

Demox Labs Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Components

Conventions

Conformance

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: demox-labs
name: Demox Labs
description: 'Demox Labs is a San Francisco company building privacy infrastructure for zero-knowledge (ZK) blockchains, starting
  with the Aleo network. It is the maker of Leo Wallet, a privacy-focused, zero-knowledge cryptocurrency wallet that constructs
  transactions locally on the user''s device and lets holders conceal or disclose any component of a transaction before it
  is verified on chain. Demox ships developer tooling for the Aleo and Polygon Miden ecosystems: the Aleo SDK and Miden SDK
  (WebAssembly builds), the Aleo and Miden wallet adapters (modular TypeScript adapters and React components for connecting
  dApps to compatible wallets), and the public Aleo RPC API, a free JSON-RPC 2.0 endpoint for reading blocks, transactions,
  transitions, records, programs, mappings, NFTs, and staking data from the Aleo network. Leo Wallet is transitioning to Shield,
  a next-generation Aleo privacy wallet built by Provable.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://raw.githubusercontent.com/api-evangelist/demox-labs/refs/heads/main/apis.yml
url: https://raw.githubusercontent.com/api-evangelist/demox-labs/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- dcvc
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Blockchain
- Zero Knowledge
- Cryptocurrency
- Wallets
- Privacy
- Web3
- Developer Tools
- SDK
- JSON-RPC
tags_raw:
- Company
- Blockchain
- Zero Knowledge
- Cryptocurrency
- Wallet
- Privacy
- Web3
- Developer Tools
- SDK
- JSON-RPC
apis:
- name: Aleo RPC API
  description: Free public JSON-RPC 2.0 API for reading the Aleo zero-knowledge blockchain — latest blocks and heights, transactions
    and transitions, records, deployed programs, mapping values, public NFTs and token programs, staking balances, and chain
    status. Also supports generating unsigned transactions and program deployments. No authentication; rate limiting may be
    applied to prevent abuse.
  humanURL: https://docs.leo.app/aleo-rpc-api
  baseURL: https://testnetbeta.aleorpc.com
  tags:
  - Blockchain
  - JSON-RPC
  - Aleo
  - Zero Knowledge
  properties:
  - type: Documentation
    url: https://docs.leo.app/aleo-rpc-api
  - type: APIReference
    url: https://docs.leo.app/aleo-rpc-api/endpoints
  - type: Authentication
    url: authentication/demox-labs-authentication.yml
  - type: Conventions
    url: conventions/demox-labs-conventions.yml
  - type: Conformance
    url: conformance/demox-labs-conformance.yml
  - type: Lifecycle
    url: lifecycle/demox-labs-lifecycle.yml
  - type: X-MCPServerCandidate
    url: mcp/demox-labs-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.leo.app/
- type: DomainSecurity
  url: security/demox-labs-domain-security.yml
- type: DeveloperPortal
  url: https://docs.leo.app
- type: Documentation
  url: https://docs.leo.app
- type: GettingStarted
  url: https://docs.leo.app
- type: APIReference
  url: https://docs.leo.app/aleo-rpc-api/endpoints
- type: Blog
  url: https://leo.app/blog
- type: Support
  url: https://help.leo.app
- type: GitHubOrganization
  url: https://github.com/demox-labs
- type: PrivacyPolicy
  url: https://leo.app/privacy
- type: TermsOfService
  url: https://leo.app/terms
- type: SignUp
  url: https://leo.app/download
- type: Packages
  url: packages/demox-labs-packages.yml
- type: SDKs
  url: packages/demox-labs-packages.yml
- type: Components
  url: components/demox-labs-components.yml
- type: Authentication
  url: authentication/demox-labs-authentication.yml
- type: Conventions
  url: conventions/demox-labs-conventions.yml
- type: Conformance
  url: conformance/demox-labs-conformance.yml
- type: Lifecycle
  url: lifecycle/demox-labs-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/demox-labs-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/demox-labs-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/demox-labs"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/demox-labs/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.