LocBox Labs website screenshot

LocBox Labs

LocBox Labs is the engineering identity behind Hownd, Inc. (formerly FetchRev, originally LocBox), a Tempe, Arizona automated promotions and local-merchant marketing platform that helps restaurants, health and beauty businesses, family entertainment centers, attractions and retail merchants generate new and repeat customers. The platform runs automated marketing across website popups, email drip and birthday campaigns, social media, buy-now promos, gift cards, a promo discovery portal, the MyHownd consumer mobile app, and guest-WiFi capture, billed at a flat monthly fee plus a share of each transaction. Merchants work in the Hownd app at hownd.app, with the legacy FetchRev merchant application still served at app.locbox.com. Hownd operates a partner-gated REST API at partner-api.hownd.com that lets approved partners manage subscribers on behalf of Hownd merchants; it is authenticated with OAuth 2.0 client-credentials against the company's Auth0 tenant and scoped per merchant with an X-Tenant-Id header. No OpenAPI, public API reference, or developer portal is published for it — the only public documentation is the first-party example repository in the company's LocBoxLabs GitHub org.

LocBox Labs publishes 1 API on the APIs.io network. Tagged areas include Company, Marketing, Promotions, Local Marketing, and Small Business.

LocBox Labs’ developer surface includes documentation, getting-started guide, pricing, engineering blog, support, authentication, and 17 more developer resources.

33.0/100 thin ▲ 17.8 Agent 12/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
AccessPaid
1 APIs
CompanyMarketingPromotionsLocal MarketingSmall BusinessAutomationCouponsEmail MarketingLoyaltyGuest WiFiFamily EntertainmentRestaurants

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 33.0/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 7.4 / 20
Commercial Clarity 14.7 / 20
Operational Transparency 0.7 / 13
Governance 1.5 / 12
Discoverability 8.7 / 10
Agent readiness — 12/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
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 7 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/locbox-labs: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Hownd Partner API

A secured REST API that lets an approved Hownd partner manage Subscribers on behalf of Hownd customers (merchants and businesses). Partners are issued OAuth 2.0 client credentia...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Locbox Labs Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Locbox Labs Authentication

oauth2 · 1 scheme

SECURITY

Locbox Labs Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: locbox-labs
name: LocBox Labs
description: LocBox Labs is the engineering identity behind Hownd, Inc. (formerly FetchRev, originally LocBox), a Tempe, Arizona
  automated promotions and local-merchant marketing platform that helps restaurants, health and beauty businesses, family
  entertainment centers, attractions and retail merchants generate new and repeat customers. The platform runs automated marketing
  across website popups, email drip and birthday campaigns, social media, buy-now promos, gift cards, a promo discovery portal,
  the MyHownd consumer mobile app, and guest-WiFi capture, billed at a flat monthly fee plus a share of each transaction.
  Merchants work in the Hownd app at hownd.app, with the legacy FetchRev merchant application still served at app.locbox.com.
  Hownd operates a partner-gated REST API at partner-api.hownd.com that lets approved partners manage subscribers on behalf
  of Hownd merchants; it is authenticated with OAuth 2.0 client-credentials against the company's Auth0 tenant and scoped
  per merchant with an X-Tenant-Id header. No OpenAPI, public API reference, or developer portal is published for it — the
  only public documentation is the first-party example repository in the company's LocBoxLabs GitHub org.
url: https://raw.githubusercontent.com/api-evangelist/locbox-labs/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: paid
  onboarding: sales
  trial: false
  try_now: false
  public: false
  label: Partner-gated
  confidence: medium
  source:
  - https://github.com/LocBoxLabs/hownd-examples
  - https://hownd.com/pricing/
  generated: '2026-08-13'
  method: searched
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-08-13'
image: https://s21429.pcdn.co/wp-content/uploads/2020/05/hownd-logo-blue.svg
tags:
- Company
- Marketing
- Promotions
- Local Marketing
- Small Business
- Automation
- Coupons
- Email Marketing
- Loyalty
- Guest WiFi
- Family Entertainment
- Restaurants
apis:
- name: Hownd Partner API
  description: A secured REST API that lets an approved Hownd partner manage Subscribers on behalf of Hownd customers (merchants
    and businesses). Partners are issued OAuth 2.0 client credentials and retrieve a bearer token from the company's Auth0
    tenant using the client_credentials grant with the audience https://partner-api.hownd.com. Every call carries an X-Tenant-Id
    header that identifies which Hownd merchant is being acted on. Hownd states the credentials are server-to-server only
    and must not be used from a browser or mobile application. Creating a subscriber requires an email address; first name,
    last name and phone number are optional. No OpenAPI or public reference is published; the surface is documented only by
    the first-party example repository below.
  humanURL: https://github.com/LocBoxLabs/hownd-examples
  baseURL: https://partner-api.hownd.com
  tags:
  - Subscribers
  - Partner API
  - Marketing
  properties:
  - type: SourceCode
    url: https://github.com/LocBoxLabs/hownd-examples
  - type: Authentication
    url: authentication/locbox-labs-authentication.yml
  - type: Conventions
    url: conventions/locbox-labs-conventions.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/locbox-labs-domain-security.yml
- type: Website
  url: https://hownd.com
- type: Documentation
  url: https://hownd.com/knowledge-base/
- type: GettingStarted
  url: https://hownd.com/quickstart/
- type: GitHubOrganization
  url: https://github.com/LocBoxLabs
- type: Pricing
  url: https://hownd.com/pricing/
- type: Plans
  url: plans/locbox-labs-plans-pricing.yml
- type: RateLimits
  url: rate-limits/locbox-labs-rate-limits.yml
- type: Login
  url: https://hownd.app/sign-in/
- type: TermsOfService
  url: https://hownd.com/terms-of-service/
- type: PrivacyPolicy
  url: https://hownd.com/privacy-policy/
- type: Compliance
  url: https://hownd.com/data-protection-addendum/
- type: Blog
  url: https://hownd.com/blog/
- type: BlogRSS
  url: https://hownd.com/feed/
- type: Support
  url: https://hownd.com/contact/
- type: Packages
  url: packages/locbox-labs-packages.yml
- type: WellKnown
  url: well-known/locbox-labs-well-known.yml
- type: Authentication
  url: authentication/locbox-labs-authentication.yml
- type: Conventions
  url: conventions/locbox-labs-conventions.yml
- type: Conformance
  url: conformance/locbox-labs-conformance.yml
- type: Lifecycle
  url: lifecycle/locbox-labs-lifecycle.yml
- type: Components
  url: components/locbox-labs-components.yml
- type: LLMsTxt
  url: llms/locbox-labs-llms.txt
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 12
  pass: local-v1
x-coverage:
  state: covered
  reason: covered
  detail: A real API was found this pass - the Hownd Partner API at partner-api.hownd.com, documented only in the company's
    own LocBoxLabs/hownd-examples repository - but no machine-readable contract is published for it anywhere, and partner
    credentials plus a per-merchant Tenant ID are issued by Hownd rather than self-served.
  evidence:
  - url: https://github.com/LocBoxLabs/hownd-examples
    status: 200
  - url: https://partner-api.hownd.com/openapi.json
    status: 404
  - url: https://hownd.auth0.com/.well-known/openid-configuration
    status: 200
  checked: '2026-08-13'