Bitski

Bitski is a Web3 wallet-as-a-service (WaaS) and NFT infrastructure provider that lets developers embed secure, hardware-backed crypto wallets and onboarding into web and mobile applications without users installing an extension. Its platform spans OAuth2/OIDC authentication, wallet creation (account-abstraction, hardware-backed, on-chain multi-sig, and seed-phrase import), and a suite of NFT Service APIs for minting, commerce (credit card, ACH, and crypto checkout), token gating, droplinks, auctions, and wallet experience data (balances, activity, portfolio, floor prices). Bitski publishes REST OpenAPI specs served from api.bitski.com, JavaScript/React and iOS SDKs, activity webhooks, and node infrastructure for EVM chains. Backed by a16z and Kindred Ventures.

Bitski publishes 5 API contracts indexed on the APIs.io network, including Activity API, Commerce API, Droplinks API, and 2 more. Tagged areas include Web3, Crypto Wallet, Wallet as a Service, NFT, and Blockchain.

The Bitski catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Bitski’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, changelog, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

43.9/100 developing ▬ flat Agent 35/100 agent ready Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 3 Agent Skills

Web3 Crypto WalletWallet as a ServiceNFT Blockchain Authentication OAuth Payments Developer Tools Company

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 43.9/100 · developing

Contract Quality 9.5 / 19

Developer Ergonomics 9.0 / 15

Access Clarity 3.2 / 15

Operational Transparency 3.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 35/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/bitski/"><img src="https://apis.io/badge/bitski/card.svg" alt="Bitski on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Quality scores 50.4 — up to +12.4 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/bitski/apis.yml: open an issue on github.com/api-evangelist/bitski to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 5

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

Bitski Activity API

The activity API from Bitski — 1 operation(s) for activity.

Bitski Commerce API

The Commerce API from Bitski — 10 operation(s) for commerce.

Bitski Droplinks API

The Droplinks API from Bitski — 3 operation(s) for droplinks.

Bitski Minting API

The Minting API from Bitski — 8 operation(s) for minting.

Bitski Token Gating API

The Token Gating API from Bitski — 3 operation(s) for token gating.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

NFT Service APIs activity API

OPEN COLLECTION

NFT Service APIs activity Commerce API

OPEN COLLECTION

NFT Service APIs activity Droplinks API

OPEN COLLECTION

NFT Service APIs activity Minting API

OPEN COLLECTION

NFT Service APIs activity Token Gating API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Sell NFTs with Bitski Commerce

AGENT SKILL

Mint an NFT with Bitski

AGENT SKILL

Token-gate access with Bitski

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Bitski Activity Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Bitski API Rules

54 rules · 46 errors 6 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Bitski Nft Service Overlay

2 actions · update · bitski-nft-service-openapi-original.json

DERIVED

Security Posture 2

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

Bitski Authentication

oauth2/http · 3 schemes

SECURITY

Bitski Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Bitski Scopes

2 scopes · clientCredentials

2 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Bitski Agentic Access

35 operations · 14 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

WellKnown

AgenticAccess

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Components

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Webhooks

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

Twitter

Twitter

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: bitski
name: Bitski
description: Bitski is a Web3 wallet-as-a-service (WaaS) and NFT infrastructure provider that lets developers embed secure,
  hardware-backed crypto wallets and onboarding into web and mobile applications without users installing an extension. Its
  platform spans OAuth2/OIDC authentication, wallet creation (account-abstraction, hardware-backed, on-chain multi-sig, and
  seed-phrase import), and a suite of NFT Service APIs for minting, commerce (credit card, ACH, and crypto checkout), token
  gating, droplinks, auctions, and wallet experience data (balances, activity, portfolio, floor prices). Bitski publishes
  REST OpenAPI specs served from api.bitski.com, JavaScript/React and iOS SDKs, activity webhooks, and node infrastructure
  for EVM chains. Backed by a16z and Kindred Ventures.
url: https://raw.githubusercontent.com/api-evangelist/bitski/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- kindred-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - 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
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://cdn.bitskistatic.com/images/favicons/favicon-2f714ec5ebed6f2ec47661e04dd1322b.png
tags:
- Web3
- Crypto Wallet
- Wallet as a Service
- NFT
- Blockchain
- Authentication
- OAuth
- Payments
- Developer Tools
- Company
tags_raw:
- Web3
- Crypto Wallet
- Wallet as a Service
- NFT
- Blockchain
- Authentication
- OAuth
- Payments
- Developer Tools
- Company
apis:
- aid: bitski:bitski-activity-api
  name: Bitski Activity API
  description: The activity API from Bitski — 1 operation(s) for activity.
  humanURL: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
  baseURL: https://api.bitski.com
  tags:
  - Activity
  tags_raw:
  - activity
  properties:
  - type: OpenAPI
    url: openapi/bitski-activity-api-openapi.yml
- aid: bitski:bitski-commerce-api
  name: Bitski Commerce API
  description: The Commerce API from Bitski — 10 operation(s) for commerce.
  humanURL: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
  baseURL: https://api.bitski.com
  tags:
  - Commerce
  properties:
  - type: OpenAPI
    url: openapi/bitski-commerce-api-openapi.yml
- aid: bitski:bitski-droplinks-api
  name: Bitski Droplinks API
  description: The Droplinks API from Bitski — 3 operation(s) for droplinks.
  humanURL: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
  baseURL: https://api.bitski.com
  tags:
  - Droplinks
  properties:
  - type: OpenAPI
    url: openapi/bitski-droplinks-api-openapi.yml
- aid: bitski:bitski-minting-api
  name: Bitski Minting API
  description: The Minting API from Bitski — 8 operation(s) for minting.
  humanURL: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
  baseURL: https://api.bitski.com
  tags:
  - Minting
  properties:
  - type: OpenAPI
    url: openapi/bitski-minting-api-openapi.yml
- aid: bitski:bitski-token-gating-api
  name: Bitski Token Gating API
  description: The Token Gating API from Bitski — 3 operation(s) for token gating.
  humanURL: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
  baseURL: https://api.bitski.com
  tags:
  - Token Gating
  properties:
  - type: OpenAPI
    url: openapi/bitski-token-gating-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/bitski-nft-service-overlay.yaml
- type: Website
  url: https://bitski.com/
- type: DeveloperPortal
  url: https://developer.bitski.com/
- type: Documentation
  url: https://docs.bitski.com/
- type: APIReference
  url: https://docs.bitski.com/wallet-as-a-service/nft-apis/overview
- type: GettingStarted
  url: https://docs.bitski.com/wallet-as-a-service/quickstart
- type: Support
  url: https://docs.bitski.com/integrations/faq
- type: Blog
  url: https://blog.bitski.com/
- type: GitHubOrganization
  url: https://github.com/BitskiCo
- type: StatusPage
  url: https://status.bitski.com/
- type: TermsOfService
  url: https://www.bitski.com/terms
- type: PrivacyPolicy
  url: https://www.bitski.com/privacy
- type: Twitter
  url: https://twitter.com/bitski
- type: Packages
  url: packages/bitski-packages.yml
- type: SDKs
  url: packages/bitski-packages.yml
- type: Components
  url: components/bitski-components.yml
- type: Authentication
  url: authentication/bitski-authentication.yml
- type: OAuthScopes
  url: scopes/bitski-scopes.yml
- type: Conventions
  url: conventions/bitski-conventions.yml
- type: ErrorCatalog
  url: errors/bitski-problem-types.yml
- type: Lifecycle
  url: lifecycle/bitski-lifecycle.yml
- type: ChangeLog
  url: changelog/bitski-changelog.yml
- type: DataModel
  url: data-model/bitski-data-model.yml
- type: Conformance
  url: conformance/bitski-conformance.yml
- type: Webhooks
  url: asyncapi/bitski-activity-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/bitski-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: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/bitski-well-known.yml
- type: AgenticAccess
  url: agentic-access/bitski-agentic-access.yml
- type: DomainSecurity
  url: security/bitski-domain-security.yml
- type: LLMsTxt
  url: llms/bitski-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Bitski API — frequently asked questions

Does Bitski have an API?

Yes. APIs.io lists 5 APIs from Bitski, including Bitski Activity API, Bitski Commerce API and Bitski Droplinks API, and 2 more.

Is there an OpenAPI specification for the Bitski API?

Yes. APIs.io indexes 5 OpenAPI specifications for Bitski, each linked for download from this page.

How do I authenticate with the Bitski API?

Bitski documents its authentication (oauth2/http · 3 schemes). The details are profiled on APIs.io as Bitski Authentication.

Is the Bitski API ready for AI agents?

Bitski has a Kin Score of 43.9 out of 100 (developing) and an Agent Readiness score of 34.7 (agent-ready), scored by API Evangelist on 2026-11-06.

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

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.