Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Hang website screenshot

Hang

Hang is a customer loyalty and engagement platform (originally a Paradigm-backed Web3 brand-loyalty company, now positioned as an AI-driven "autonomous marketing system") used by restaurant, beauty, apparel, and e-commerce brands to build and run tier-based membership and rewards programs. Its Partner API powers program memberships, points and activities, quests, challenges, puzzles, loot/mystery boxes, rewards and redemptions, balance/gift cards, tokenized rewards, program tiers and segments, plus point-of-sale integrations with Toast and Square and real-time webhooks. Brands can embed a white-labeled rewards portal or drive the whole loyalty experience programmatically through the REST API.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Hang the way a machine reads it — 24 machine-readable artifacts across 18 APIs, 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 — Hang scores 53.8/100 (developing), with a separate agent-readiness read of 65/100 (agent native). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 53.8/100 · developing
Contract Quality 15.1 / 25
Developer Ergonomics 12.2 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 4.4 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 65/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 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

How we profile Hang

Each block below is one kind of artifact we hold for Hang. 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.

APIs 18

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

Hang Activities API

The Activities API from Hang — 2 operation(s) for activities.

Hang Loot Box Reward Choices API

The Loot Box Reward Choices API from Hang — 2 operation(s) for loot box reward choices.

Hang Loot box reward probabilities API

The Loot box reward probabilities API from Hang — 2 operation(s) for loot box reward probabilities.

Hang Loot Boxes API

The Loot Boxes API from Hang — 4 operation(s) for loot boxes.

Hang Member Actions API

The Member Actions API from Hang — 3 operation(s) for member actions.

Hang Memberships API

The Memberships API from Hang — 10 operation(s) for memberships.

Hang Program memberships API

The Program memberships API from Hang — 3 operation(s) for program memberships.

Hang Program Tiers API

The Program Tiers API from Hang — 1 operation(s) for program tiers.

Hang ProgramMembershipPuzzles API

The ProgramMembershipPuzzles API from Hang — 3 operation(s) for programmembershippuzzles.

Hang Programs API

The Programs API from Hang — 2 operation(s) for programs.

Hang Puzzles API

The Puzzles API from Hang — 4 operation(s) for puzzles.

Hang Quests API

The Quests API from Hang — 9 operation(s) for quests.

Hang Redemptions API

The Redemptions API from Hang — 4 operation(s) for redemptions.

Hang Rewards API

The Rewards API from Hang — 5 operation(s) for rewards.

Hang TokenizedRewards API

The TokenizedRewards API from Hang — 2 operation(s) for tokenizedrewards.

Hang Tokens API

The Tokens API from Hang — 7 operation(s) for tokens.

Hang Users API

The Users API from Hang — 1 operation(s) for users.

Hang Wallet Integration API

The Wallet Integration API from Hang — 2 operation(s) for wallet integration.

Scroll within the panel for all 18 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

hang-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

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

Hang Webhooks

ASYNCAPI

Security Posture 4

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.

Hang Authentication

apiKey · 1 scheme

SECURITY

Hang Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Hang Vulnerability Disclosure

contact published

SECURITY

Hang Trust Center

SOC 2, ISO 27001, GDPR

SECURITY

Resources

Every other property we hold for Hang — 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 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/hang · machine-readable index on apis.io