Here Not There Labs

Here Not There Labs (Here Not There, Inc., operating as hntlabs.com) is the a16z-backed company behind Towns Protocol, an open, decentralized messaging protocol built on Base (an Ethereum L2) that powers ownable, programmable group chat spaces, memberships, direct messages, and decentralized finance. The protocol is delivered to builders as a set of first-party TypeScript packages under the @towns-protocol npm scope (client SDK, React SDK, bot framework, encryption, and generated protobuf bindings), a Connect/gRPC Stream RPC surface defined in public .proto files, a bot/app framework with a webhook-driven event model, and end-to-end message encryption. Spaces, memberships, roles, and entitlements are enforced by on-chain smart contracts, and a network of Stream Nodes run by node operators carries encrypted message streams. This profile was surfaced as an a16z portfolio lead and enriched from the company's public developer surface (docs.towns.com, app.towns.com, the towns-protocol GitHub organization, and npm).

Here Not There Labs is listed with 1 API on the APIs.io network. Tagged areas include Company, Messaging, Decentralized, Web3, and Blockchain.

The Here Not There Labs catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Here Not There Labs’ developer surface includes documentation, API reference, getting-started guide, signup flow, CLI, authentication, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.8/100 thin ▬ flat Agent 21/100 agent aware Front door AI 1/6 silent Heartbeat 38/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 2 Agent Skills

Company Messaging Decentralized Web3 Blockchain Protocol Chat Bots Encryption SDK

Kin Score

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

Composite quality — 32.8/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 9.6 / 17

Access Clarity 1.3 / 17

Operational Transparency 1.2 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.2 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 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 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 Horizontal (data, software, accessibility, platform) 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/.

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/here-not-there-labs/"><img src="https://apis.io/badge/here-not-there-labs/card.svg" alt="Here Not There Labs 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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)

9 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 7.9 — up to +18.4 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Operational Transparency scores 10.5 — up to +11.6 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/here-not-there-labs/apis.yml: open an issue on github.com/api-evangelist/here-not-there-labs 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Matrix Protocol Ecosystem (Matrix.org Foundation directory)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

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

Towns Protocol

Towns Protocol is an open, decentralized messaging protocol built on Base. Builders integrate via first-party TypeScript SDKs, a React SDK of hooks, and a bot/app framework. Und...

Agent Skills 2

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

build-towns-bot

AGENT SKILL

create-space-and-send-message

AGENT SKILL

Event Specifications 1

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

Here Not There Labs Bot Events

ASYNCAPI

Security Posture 2

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

Here Not There Labs Authentication

5 schemes

SECURITY

Here Not There Labs Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

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

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Webhooks

Webhooks

Conventions

Conventions

Conformance

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Protobuf

Protobuf

Source (apis.yml)

aid: here-not-there-labs
name: Here Not There Labs
description: Here Not There Labs (Here Not There, Inc., operating as hntlabs.com) is the a16z-backed company behind Towns
  Protocol, an open, decentralized messaging protocol built on Base (an Ethereum L2) that powers ownable, programmable group
  chat spaces, memberships, direct messages, and decentralized finance. The protocol is delivered to builders as a set of
  first-party TypeScript packages under the @towns-protocol npm scope (client SDK, React SDK, bot framework, encryption, and
  generated protobuf bindings), a Connect/gRPC Stream RPC surface defined in public .proto files, a bot/app framework with
  a webhook-driven event model, and end-to-end message encryption. Spaces, memberships, roles, and entitlements are enforced
  by on-chain smart contracts, and a network of Stream Nodes run by node operators carries encrypted message streams. This
  profile was surfaced as an a16z portfolio lead and enriched from the company's public developer surface (docs.towns.com,
  app.towns.com, the towns-protocol GitHub organization, and npm).
url: https://raw.githubusercontent.com/api-evangelist/here-not-there-labs/refs/heads/main/apis.yml
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
  - security
  generated: '2026-11-06'
  method: derived
image: https://towns.com/ogtowns.jpg
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
x-tier: profiled
x-tier-reason: portfolio-lead-enriched
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
tags:
- Company
- Messaging
- Decentralized
- Web3
- Blockchain
- Protocol
- Chat
- Bots
- Encryption
- SDK
apis:
- name: Towns Protocol
  description: Towns Protocol is an open, decentralized messaging protocol built on Base. Builders integrate via first-party
    TypeScript SDKs, a React SDK of hooks, and a bot/app framework. Under the hood the network exposes a Connect/gRPC Stream
    RPC service (StreamService, AppRegistryService, AuthenticationService) defined in public protobuf files, with end-to-end
    encrypted message streams carried by Stream Nodes and spaces/memberships/entitlements enforced by on-chain smart contracts.
  humanURL: https://docs.towns.com
  baseURL: https://app.towns.com
  tags:
  - Messaging
  - Web3
  - Protocol
  - Bots
  - gRPC
  properties:
  - type: Documentation
    url: https://docs.towns.com
  - type: GettingStarted
    url: https://docs.towns.com/build/bots/getting-started
  - type: Protobuf
    url: grpc/here-not-there-labs-protocol.proto
  - type: Protobuf
    url: grpc/here-not-there-labs-apps.proto
  - type: Protobuf
    url: grpc/here-not-there-labs-auth.proto
  - type: Protobuf
    url: grpc/here-not-there-labs-payloads.proto
  - type: Webhooks
    url: asyncapi/here-not-there-labs-bot-events.yml
  - type: Authentication
    url: authentication/here-not-there-labs-authentication.yml
  - type: Conventions
    url: conventions/here-not-there-labs-conventions.yml
common:
- type: DomainSecurity
  url: security/here-not-there-labs-domain-security.yml
- type: Website
  url: https://www.towns.com
- type: DeveloperPortal
  url: https://app.towns.com/developer
- type: Documentation
  url: https://docs.towns.com
- type: APIReference
  url: https://docs.towns.com/build/react-sdk/getting-started
- type: GettingStarted
  url: https://docs.towns.com/build/bots/getting-started
- type: GitHubOrganization
  url: https://github.com/towns-protocol
- type: SignUp
  url: https://app.towns.com/developer
- type: LLMsTxt
  url: llms/here-not-there-labs-llms.txt
- type: Packages
  url: packages/here-not-there-labs-packages.yml
- type: SDKs
  url: packages/here-not-there-labs-packages.yml
- type: CLI
  url: cli/here-not-there-labs-cli.yml
- type: Protobuf
  url: grpc/here-not-there-labs-protocol.proto
- type: Webhooks
  url: asyncapi/here-not-there-labs-bot-events.yml
- type: Conventions
  url: conventions/here-not-there-labs-conventions.yml
- type: Authentication
  url: authentication/here-not-there-labs-authentication.yml
- type: Conformance
  url: conformance/here-not-there-labs-conformance.yml
- type: Compliance
  url: conformance/here-not-there-labs-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Here Not There Labs API — frequently asked questions

Does Here Not There Labs have an API?

Yes. APIs.io lists 1 API from Here Not There Labs, including Towns Protocol.

How do I authenticate with the Here Not There Labs API?

Here Not There Labs uses bearer-token authentication (5 schemes). The details are profiled on APIs.io as Here Not There Labs Authentication.

Is the Here Not There Labs API ready for AI agents?

Here Not There Labs has a Kin Score of 32.8 out of 100 (thin) and an Agent Readiness score of 20.7 (agent-aware), 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/here-not-there-labs"

All providers

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

Every operation they expose

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

How their score was established

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